*** 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
*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
** This bug is no longer a duplicate of bug 1295774
ERROR processing policydb rules for profile lxc-container-default, failed to
load
** This bug has been marked a duplicate of bug 1296459
Upgrade
It fails.
I would say the problem is that
/etc/apparmor.d/lxc/lxc-default
includes a file named
lxc-container-default
which simply is missing in the package and thus can't be included.
# /etc/init.d/apparmor reload
* Reloading AppArmor profiles
*** This bug is a duplicate of bug 1295774 ***
https://bugs.launchpad.net/bugs/1295774
Nope, lxc-container-default is the profile name, there doesn't have to
be a matching file name.
However the log your provided tells me which apparmor bug you are
hitting, I'll mark this bug as a duplicate
uncommenting
lxc.aa_profile = unconfined
in the config made the machine run again, but still spit out error
messages.
--
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/1296681
Title:
What happens if you do sudo /etc/init.d/apparmor reload and then try
the container again with lxc.aa_profile = unconfined commented?
We have a couple of apparmor regressions which happened with the latest
apparmor upload and that the security is tracking down, I'm just not
sure which you are