[Bug 1325468] Re: [systemd] container startup fails with AppArmor
Martin Pitt
martin.pitt at ubuntu.com
Mon Jun 2 15:08:55 UTC 2014
Oh, I missed the "lxc-start: No such file or directory - failed to
change apparmor profile to lxc-container-default". I didn't run the
equivalents of /etc/init/lxc.conf. "sudo /etc/init.d/apparmor reload"
seems to have understood the new line (mount options in rw, slave,), but
when I manually run the equivalent of that upstart job, I get an error:
$ sudo /lib/init/apparmor-profile-load usr.bin.lxc-start
AppArmor-Parser-Fehler f?r /etc/apparmor.d/usr.bin.lxc-start in /etc/apparmor.d/abstractions/lxc/start-container in Zeile 16: syntax error, unexpected TOK_ID, expecting TOK_END_OF_RULE or TOK_ARROW
The syntax indeed looks a bit curious as it's using the comma both for
separating mount options as well as separating entire rules, so this
might not be entirely correct.
--
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/1325468
Title:
[systemd] container startup fails with AppArmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions
More information about the Ubuntu-server-bugs
mailing list