This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu5 --------------- lxc (0.8.0~rc1-4ubuntu5) quantal; urgency=low
* 0082-umount-old-proc: fix proc auto-mount. If /proc is already mounted, make sure that /proc/self points to 1, since we are container init. Otherwise, assume proc is an old one, and umount it and remount our own. If we keep the old proc mounted, apparmor transitions will by tried for wrong task and fail. Also move check for whether apparmor is enabled so that it is called by lxc-execute. (LP: #993706) * update 0074-lxc-execute-find-init to look for lxc-init in LXCINITDIR/lxc/lxc-init * debian/control: add cloud-utils to lxc Recommends, as lxc-ubuntu-cloud needs it. (LP: 995361) * debian/lxc.upstart: load apparmor profiles before auto-starting containers. (LP: #989853) * pop 06-bash.patch and 0075-lxc-ls-bash. lxc-clone also has bashims, just stick to using bash until upstream is also converted (so we are safe against patches). -- Serge Hallyn <serge.hal...@ubuntu.com> Mon, 07 May 2012 21:22:26 +0000 ** Changed in: lxc (Ubuntu Quantal) Status: Confirmed => 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/993706 Title: Fix lxc-execute without rootfs failing apparmor transitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/993706/+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