On Fri, Nov 21, 2014 at 05:24:19PM -0500, Michael H. Warfield wrote: > On Fri, 2014-11-21 at 04:41 +0000, Serge Hallyn wrote: > > Quoting Antonio Terceiro ([email protected]): > > > Containers with systemd need a somewhat special setup, which I borrowed > > > and adaptec from lxc-fedora. These changes are required so that Debian 8 > > > (jessie) containers work properly, and are a no-op for previous Debian > > > versions. > > > > > > Signed-off-by: Antonio Terceiro <[email protected]> > > > Michael and/or Stéphane may have other comments , but as you say this > > will not regress non-systemd hosts so looks like a step in the right > > direction to me, thanks. > > While I did add code to the config.c file to detect systemd as the init > system and default it to enabling autodev, I would recommend adding > "lxc.autodev = 1" to containers generated by the template that are known > to be using systemd. It can't go into the common config files because > of variability in distro revs and systemd utilization and still leaves > open the problem when a container is upgraded to a systemd release from > a non-systemd release, but that's what the runtime code is there for. > > There's also the problem with lxc.kmsg and systemd-journald which, I > guess, doesn't impact this case because Debian is using systemd but not > journald? I haven't confirmed that but noticed it in some articles. If > journald is being used, you have to set "lxc.kmsg = 0" or journald will > end up in a messaging echo loop between /dev/console and /dev/kmsg.
Thanks for the feedback. I will post an updated patch soon. -- Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ lxc-devel mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-devel
