Quoting Tim Spriggs (t...@arizona.edu):
> Thanks for the quick fix! Unfortunately, something else broke when I
> pulled that package from the trusty repository. The lxc instance is
> started but nothing runs. Starting it manually vs on boot produces the
> same behavior and I only see these two lines when I start manually:
>
> <4>init: console-setup main process (46) terminated with status 1
> <30>systemd-udevd[58]: starting version 204
>
>
> Furthermore, there are only two processes running, rsyslogd and (after a
> painful dist-upgrade inside the lxc root) systemd-udevd.
>
> Rolling back to 1.0.0~alpha1-0ubuntu13 allows me to start the instance
> again (albeit manually).
Hi,
simply pulling the packages from trusty should not have worked, as they
depend on libseccomp2 which is not available in saucy. Could you tell
us exactly what you installed?
The hang you are seeing now typically happens when the container fstab
specifies something which fails to mount (often refused by apparmor)
so that mountall hangs. Could you please file a new bug for that issue,
specifying exactly how the container was created, what package versions
exactly you are running on what release, and outputfile resulting from
lxc-start -n containername -l info -o outputfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
