Re: [Bug 1347020] Re: systemd does not boot in a container
@Jens this is very dependent on your exact setup, so please open a new bug specifying your precise host environment (release, any ppas, package versions, any custom configuration, and error logs if possible) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Today I upgraded our last utopic containers (~10) to vivid using do- release-upgrade: Everywhere the same: after reboot systemd is the only thing which is running in the container, but nothing else happens. It doesn't start anything! So the only way to get the stuff fixed is to manually attach to the container, do a ' ln -sf upstart /sbin/init', logout and force a lxc-stop/start of the container and do the remaining things ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
The problem is fixed but needs additional comment. I've had a problem after upgrading only lxc package from trusty-backports. The network was not working in debian jessie and after logging in (lxc-attach) systemd was not working correctly. The solution was to update not only lxc package but also lxc-templates and recreate guest OS. rm -rf /var/cache/lxc/debian # remove cached debian template apt-get install -t trusty-backports lxc lxc-templates # update both lxc and lxc-templates After that it works without a problem. Thank you for the fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Fixed through trusty-backports. ** Changed in: lxc (Ubuntu Trusty) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
I'm usingTrusty (14.04.2) trying to run debian/jessie in lxc what i did: $ add-apt-repository ppa:ubuntu-lxc/daily $ apt-get update $ apt-get install lxc cgmanager lxcfs then: $ lxc-create -n jessie -t debian $ lxc-start -n jessie nothing seems to happen in the syslog i see: Jul 31 20:07:05 ubu kernel: [ 962.944281] type=1400 audit(1438366025.666:88): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/cgroup/cpu,cpuacct/ pid=15251 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, noexec Jul 31 20:07:05 ubu kernel: [ 962.944321] type=1400 audit(1438366025.666:89): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/cgroup/ pid=15251 comm=systemd flags=ro, nosuid, nodev, noexec, remount, strictatime but it's actually running, i can get a shell with: $ lxc-attach -n jessie root@jessie:~# so there is just the login part missing for some reason (init/systemd won't start getty?) Thanks Stephane for the PPA! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
I'm running utopic with latest updates. Any container, which has systemd running simply hangs, when /sbin/init gets started (no matter, whether config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and today with a vivid container. So wondering, whether there is a bugfix available at all? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Thank you Stephane for your PPA! I installed 14.04 expecting LXC to just work, found that it didn't, somehow found this page, installed your PPA and the updated utilities and it now appears to be working perfectly! I only wish it would work out of the box in an LTS release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Any ideas when this will be fixed in Trusty? This is blocking unity8-lxc from working anymore on Trusty hosts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Not anytime soon unfortunately. The backport of all the needed bits as SRUs will be very very tricky to get right, currently our timeframe is by 16.04. If you're maintaining a PPA already, you could pick up the required trusty packages from ppa:ubuntu-lxc/daily or just include your own backports of cgmanager, lxcfs and lxc. They all work great on trusty (that's what I'm using here) but we can't just push them as is into a stable release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
With latest lxc and lxcfs this works now, both system and session containers with systemd, with systemd on the host. ** Changed in: lxc (Ubuntu) Status: Triaged = Fix Released ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) = Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
** Changed in: lxc (Ubuntu) Assignee: (unassigned) = Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu) Milestone: None = ubuntu-15.01 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
Retitling the bug to be more general, and adding a trusty task to reflect the original trusty host part. This was discussed on UOS last week (https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd- migration). The intention is to make this work on vivid first, and then backport a newer LXC (or possibly just some patches) to trusty so that systemd containers work on trusty as well. ** Summary changed: - trusty host - utopic lxc container cloudimage boot with systemd does not work + systemd does not boot in a container ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Trusty) Status: New = Triaged ** Changed in: lxc (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
I prepared a minimal vivid container with systemd-sysv, and tried to
boot it (vivid host):
$ sudo lxc-start -n vivid-systemd -F
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
[... hangs ...]
In apparmor I see:
[10072.122514] audit: type=1400 audit(1416213339.298:50): apparmor=DENIED
operation=mount info=failed type match error=-13
profile=lxc-container-default name=/sys/fs/cgroup/systemd/ pid=16469
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev,
noexec
After setting lxc.aa_profile = unconfined, the container boots (with
similar error message spew as in #1, which we can ignore for now), but
logging in on the console takes a long time. systemd-journal (in the
guest) starts spinning the CPU to 100%. sudo journalctl shows me the
logs. stracing shows
read(9, , 8192) = 0
epoll_wait(7, {{EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3073693008,
u64=140547288520016}}, {EPOLLIN, {u32=3073692768, u64=140547288519776}},
{EPOLLIN, {u32=3073692288, u64=140547288519296}}, {EPOLLIN, {u32=3073692528,
u64=140547288519536}}}, 14, 0) = 4
clock_gettime(0x7 /* CLOCK_??? */, {10618, 410721720}) = 0
writev(2, [{/dev/kmsg buffer overrun, some m..., 45}, {\n, 1}], 2) = 46
I tried to set lxc.kmsg = 0 as Serge indicated in comment 2, but this
doesn't seem to have the intended effect: in the container I still see
/dev/kmsg - console.
For the record: booting and journal work fine in systemd-nspawn; but
this has neither apparmor protection nor does it do the /dev/kmsg -
/dev/lxc/console trick; instead, /dev/kmsg does not exist at all there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1347020
Title:
systemd does not boot in a container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
