*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
I seem to be seeing this issue as well. I'm not sure if its the
duplicate issue.
The profile config file name is "lxc-default-with-mounting" yet the
actual profile name appears to be changed to "lxc-container-default-
with-mounting" causing confusion.
/etc/apparmor.d/lxc/lxc-default-with-mounting
Inside that file the profile name is "lxc-container-default-with-
mounting". I presume that at some point the profile naming convention
was changed from "lxc-default" to "lxc-container-default" but the file
name didn't get changed to match the convention.
This is confusing because if I configure the apparmor profile in the lxc
config based on the config filename I'll get an error:
lxc.aa_profile = lxc-default-with-mounting
error:
lxc-start: No such file or directory - failed to change apparmor profile
to lxc-default-with-mounting
using the actual profile name from inside the file "lxc.aa_profile =
lxc-container-default-with-mounting" solves the problem.
I think a solution to the multiple names confusion would be to rename:
/etc/apparmor.d/lxc/lxc-default-with-mounting
to
/etc/apparmor.d/lxc/lxc-container-default-with-mounting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296681
Title:
failed to change apparmor profile to lxc-container-default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1296681/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
