Public bug reported: This bug affects all arkose containers.
Since the recent change to implement per-container apparmor profile, arkose stopped working, printing: lxc-start: No such file or directory - failed to change apparmor profile to lxc-container-default Trying to reproduce this with a standard container, I tracked it down to the lack of /proc defined in LXC's fstab. Arkose usually starts the container without giving lxc a fstab file, then after that mounts some file systems, I should change that anyway and will do so post-beta2 but the problem remains that it's currently impossible to start a container that doesn't use lxc's fstab to mount /proc. On top of arkose container, this also breaks anyone using my recommended setup to boot VM images in a container per http://www.stgraber.org/2012/03/04/booting-an-ubuntu-12-04-virtual- machine-in-an-lxc-container/ ** Affects: lxc (Ubuntu) Importance: High Status: Triaged ** Affects: lxc (Ubuntu Precise) Importance: High Status: Triaged ** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Precise) Status: New => Triaged ** Changed in: lxc (Ubuntu Precise) Importance: Undecided => High ** Changed in: lxc (Ubuntu Precise) Milestone: None => ubuntu-12.04-beta-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963388 Title: Unable to start containers without proc entry in fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/963388/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
