On Sat, 07.12.13 23:56, Colin Guthrie ([email protected]) wrote: > 'Twas brillig, and Canek Peláez Valdés at 05/12/13 23:26 did gyre and > gimble: > > Hi; I've been playing with systemd-nspawn with Gentoo. I'm running > > systemd 208, and the normal Gentoo stage3 image [1], installing > > systemd 204 inside it. Everything works great, but for some reason > > after powering off the container, the file system where it resides > > gets remounted read-only. I should notice that this is a file system > > different from /. > > Interesting. Can't say I've seen this personally. Only thing I've seen > that is even semi related is that when playing with containers recently, > the service inside the container that remounts root filesystem rw > failed. Not seem much else other than that tho'. > > > Also, I usually need to machinectl terminate the machine, otherwise I > > cannot start the same container with the same name (I think this is a > > known bug). > > Yeah known bug, but when I played with kernel 3.12.3 today I didn't see > it and started the same machine twice without any problem... So maybe > it's fixed (or maybe I was just lucky!)
It's systemd that has a work-around now, the kernel changed nothing, as the stupid interface it has is actually intended that way. With Tejun's "sane behaviour" cgroup rework we will however get a completely new notification scheme which won't be as braindead... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
