[Bug 1296681] Re: failed to change apparmor profile to lxc-container-default

[Stéphane Graber]

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 hitting...

-- 
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:
  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