Public bug reported:
== 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.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1117589
Title:
Ubuntu containers fails to start on UEFI-enabled hosts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1117589/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
