This bug was fixed in the package lxc - 0.9.0~alpha3-0ubuntu3
---
lxc (0.9.0~alpha3-0ubuntu3) raring; urgency=low
* 0001-fix-race-with-fast-init: Before starting lxc_mainloop, check whether
lxc-init has already exited. If it has, return immediately to reap it.
(LP:
This bug was fixed in the package lxc - 0.9.0~alpha3-0ubuntu3
---
lxc (0.9.0~alpha3-0ubuntu3) raring; urgency=low
* 0001-fix-race-with-fast-init: Before starting lxc_mainloop, check whether
lxc-init has already exited. If it has, return immediately to reap it.
(LP:
Thanks for reporting this bug. Confirmed in raring.
I note that there is a blueprint item for Daniel Lezcano to improve the
monitoring code to be more robust. I suspect that will solve this
issue.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Thanks for reporting this bug. Confirmed in raring.
I note that there is a blueprint item for Daniel Lezcano to improve the
monitoring code to be more robust. I suspect that will solve this
issue.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)