Hi, On Sun, Dec 03 2017 13:47:29 +0100, Michael Biebl wrote: > > There is an upstream fix for this in > > https://github.com/systemd/systemd/pull/4693 -- > > acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually > > fixes read-only containers, but it requires two other commits to apply > > cleanly. I applied the following sequence to systemd-container on > > stretch: > > > > https://github.com/systemd/systemd/commit/bdb4e0cb646ff33ecbb1cf4b502870f84bf4016d > > https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e > > https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b > > > > and it solved my problem. Could you backport these patches to stretch? > > > > Those patches looks a bit invasive for a stretch stable upload. > But we do provide updated systemd versions with this fix via > stretch-backports: > https://packages.debian.org/source/stable-backports/systemd > > Would that be sufficient for your case?
It turned out that we needed a couple other patches for systemd-container, including one yet to be released, so for our case it's sufficient to do nothing since we now use our own systemd-container package :) However, I don't think the patches I listed are that invasive -- note that they only affect the systemd-nspawn binary. Anyone else having a problem with --read-only can move to the backports package, yes, but we explicitly did not want to upgrade all of systemd just to get a few patches to nspawn. _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
