Note that the lxc-execute profile will need to be more lenient than the
lxc-start one.
@afcowie, if you'd like to propose a patch for this, please feel free,
as I won't be able to do it this week.
** This bug is no longer a duplicate of bug 981955
lxc-execute without config does not seem to wo
*** This bug is a duplicate of bug 981955 ***
https://bugs.launchpad.net/bugs/981955
Quoting Andrew Cowie (and...@operationaldynamics.com):
> *** This bug is a duplicate of bug 981955 ***
> https://bugs.launchpad.net/bugs/981955
>
> Thanks for that. But shouldn't the fix (vice workaround)
*** 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
*** This bug is a duplicate of bug 981955 ***
https://bugs.launchpad.net/bugs/981955
thanks for reporting this bug. It is a duplicate of bug 981955. The
workaround documented there is to do:
cat > test.conf << EOF
lxc.aa_profile = unconfined
lxc.rootfs = /
EOF
lxc-execute -n test -f test.c
