Actually, running "sudo unity8-lxc-setup" has a start/wait/attach sequence that is causing failures. Another way I try to reproduce after the whole container is setup is to create a little script with the following:
lxc-start -n unity8-lxc lxc-wait -t 5 -s RUNNING -n unity8-lxc lxc-attach -n unity8-lxc -- uname -a Run that as sudo since it's privileged and I can sometimes get the apparmor error. Keep in mind that after the container starts for the first time, I have never been able to reproduce this issue unless I reboot. Just doing a lxc-stop is not enough. Also, if you still need some help, you can ping me on irc @ ChrisTownsend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452451 Title: failed to change apparmor profile to lxc-container-default-with- nesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs