On 03/21/2012 03:41 PM, Serge Hallyn wrote:
> Thanks for reporting this bug.
>
> To work around this, you should be able to do:
>
> sudo sed -i 's/umount.*$/umount,/' /etc/apparmor.d/usr.bin.lxc-start
> sudo apparmor_parser -r /etc/apparmor.d/usr.bin.lxc-start
>
> ** Changed in: lxc (Ubuntu)
>
This bug was fixed in the package lxc - 0.7.5-3ubuntu43
---
lxc (0.7.5-3ubuntu43) precise; urgency=low
* lxc.apparmor: allow all umount activity in lxc-start (LP: #961536)
-- Serge HallynWed, 21 Mar 2012 14:49:14 -0500
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fi
Thanks for reporting this bug.
To work around this, you should be able to do:
sudo sed -i 's/umount.*$/umount,/' /etc/apparmor.d/usr.bin.lxc-start
sudo apparmor_parser -r /etc/apparmor.d/usr.bin.lxc-start
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
** Description changed:
+ I'm getting the following with the most recent update. Logs will follow:
+
+ $sudo lxc-start -n u1-server
+ lxc-start: Permission denied - failed to umount 'dev/pts'
+ lxc-start: failed to setup the new pts instance
+ lxc-start: failed to setup the container
+ lxc-start:
