[Bug 989853] [NEW] autostart containers must be started after apparmor profiles are loaded
Serge Hallyn
989853 at bugs.launchpad.net
Fri Apr 27 15:59:21 UTC 2012
Public bug reported:
lxc.conf currently does the container autostarts before it loads the
apparmor profiles. That is wrong.
Perhaps the container autostart should be done from start and not pre-
start? But at least those must be reversed.
** Affects: lxc (Ubuntu)
Importance: High
Status: Confirmed
** Affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
** Affects: lxc (Ubuntu Quantal)
Importance: High
Status: Confirmed
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Quantal)
Importance: High
Status: Confirmed
--
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/989853
Title:
autostart containers must be started after apparmor profiles are
loaded
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/989853/+subscriptions
More information about the Ubuntu-server-bugs
mailing list