Pleased to report that the fix to lxc reached us through our mirror
today (!) and that lxc-execute is working now. Nicely done.
AfC
** Changed in: lxc (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server T
Is lxc 0.8.0 going to be updated into Precise? This bug is pretty
annoying; and while I appreciate there is a workaround, it seems adding
an extra config entry to lxc-excute invocation just to avoid an apparmor
failure is a bit much to ask of users.
AfC
--
You received this bug notification beca
*** This bug is a duplicate of bug 981955 ***
https://bugs.launchpad.net/bugs/981955
Thanks for that. But shouldn't the fix (vice workaround) be adding an
entry for lxc-execute to /etc/apparmor.d/ ?
AfC
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
Public bug reported:
On a Precise system, LXC is no longer working:
# lxc-execute -n foo /bin/bash
lxc-execute: Permission denied - failed to change apparmor profile to
lxc-container-default
lxc-execute: invalid sequence number 1. expected 2
lxc-execute: failed to spawn 'foo'
#
At a minimum, I'
