Hello Michael, Evgeni, Evgeni Golov [2016-07-18 7:25 +0200]: > > > There is no point in even wasting four getty processes on tty1-4 in > > > LXC -- containers are not meant to have gettys on ttys in the first > > > place. I committed a fix to git for that. > > > (ConditionVirtualization=!container) > > this will break lxc-console, but more later :)
console-getty.service suffices for that -- this is running in containers. Interestingly I also have container-getty@{0,..3}.service running. "lxc-start -n mycontainer -F" also works, i. e. you see the boot messages. > > I just created a test jessie lxc container (using lxc 2.0.0-3~bpo8+1) on > > jessie host system (using lxc-create -t download) > > -t debian please, -t download will download an image from > linuxcontainers.org, which might or might not be the same as -t debian. > (AFAIK it is almost identical, but please don't file bugs if it isn't > ;)) The "download" images are built from the exact same templates. Using the "debian" template will do the exact same things, check /usr/share/lxc/templates/lxc-debian . This has those modifications. I do remember that Stèphane Graber (LXC upstream) was bugging me about fixing sigpwr.target in systemd proper (https://lists.linuxcontainers.org/pipermail/lxc-users/2015-May/009279.html and https://launchpad.net/bugs/1457321), the udev stuff isn't necessary at all as udev will already not start in LXC due to ConditionPathIsReadWrite=/sys, and the getty modifications should now be obsolete too. The lxc-ubuntu template does none of these modifications, and it works fine. So indeed they should be dropped from the lxc-debian template as well. (This should be done upstream). Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)