** Tags removed: needssru
--
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
This bug was fixed in the package lxc - 0.7.5-3ubuntu56
---
lxc (0.7.5-3ubuntu56) precise-proposed; urgency=low
* Fix Ubuntu template to install the host architecture of the required
mutli-arch packages (when using qemu-user-static) instead of hardcoded
amd64 version. (LP:
Fix confirmed here, stop/start of lxc after the update loads the needed
apparmor profile and starts the container as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:ubuntu/precise-proposed/lxc
--
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
Hello Serge, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
** Changed in: lxc (Ubuntu Quantal)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Tags added: needssru
--
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:
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu5
---
lxc (0.8.0~rc1-4ubuntu5) quantal; urgency=low
* 0082-umount-old-proc: fix proc auto-mount. If /proc is already mounted,
make sure that /proc/self points to 1, since we are container init.
Otherwise, assume proc
** Branch linked: lp:ubuntu/lxc
--
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
** Description changed:
lxc.conf currently does the container autostarts before it loads the
- apparmor profiles. That is wrong.
+ apparmor profiles. That is wrong. Those must be reversed.
- Perhaps the container autostart should be done from start and not pre-
- start? But at least
** Description changed:
lxc.conf currently does the container autostarts before it loads the
apparmor profiles. That is wrong. Those must be reversed.
==
SRU Justification
1. Impact: auto-start containers could be started without apparmor enforcement
2.
10 matches
Mail list logo
