This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu45
---
lxc (0.8.0~rc1-4ubuntu45) raring; urgency=low
[ Stéphane Graber ]
* Allow the container to mount efivars on /sys/firmware/efi/efivars.
efivars is automatically mounted by mountall on UEFI systems, failure to
Sorry, I'm going to postpone pushing this until wednesday until I have a
chance to run some more tests (which I will do tomorrow).
--
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/1049908
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New = 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/1049908
Thanks for the merge proposal. That's quite neat.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
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/1049908
Title:
Upstart
I see one problem with that. Directly calling lxc-stop outside of the
container, or half in the container will cause upstart to restart it,
which isn't quite what we want.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I see one problem with that. Directly calling lxc-stop outside of the
container, or half in the container will cause upstart to restart it,
which isn't quite what we want.
I explicitly did not add the 'respawn' stanza to the .conf file, I just
mentioned it as a possible and valid use case. The
Oh right, sorry, for some reason I thought respawn was the default.
--
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/1049908
Title:
Upstart control of lxc container instances
To manage
