Ubuntu containers fails to start on UEFI-enabled hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Stéphane Graber | ||
Quantal |
Fix Released
|
Undecided
|
Stéphane Graber |
Bug Description
== Rationale ==
Ubuntu introduced the use of the efivars filesystem for UEFI hosts and it's been backported to current stable releases.
On machines running UEFI, mountall will attempt to mount the efivars filesystem, even in containers.
Unfortunately our apparmor profile prevents that and as a result the container completely fails to boot.
The problem was easily fixed in raring but we need to have this backported to precise and quantal.
== Test case ==
1) Find a system running Ubuntu on UEFI
2) lxc-create -t ubuntu -n p1
3) lxc-start -n p1
4) Just boot fine where it used to fail prior to the update.
== Regression potential ==
None that I can think of, the change only allows the extra filesystem in apparmor and prevent any actual access to it, so from a user perspective, they don't actually get access to anything new.
Changed in lxc (Ubuntu): | |
status: | New → Fix Released |
Changed in lxc (Ubuntu Precise): | |
assignee: | nobody → Stéphane Graber (stgraber) |
status: | New → In Progress |
Changed in lxc (Ubuntu Quantal): | |
assignee: | nobody → Stéphane Graber (stgraber) |
Changed in lxc (Ubuntu Quantal): | |
status: | New → In Progress |
Hello Stéphane, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ lxc/0.8. 0~rc1-4ubuntu39 .12.10. 2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!