lxc init script should fail when it ... failed
Bug #925511 reported by
Serge Hallyn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dnsmasq (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
In particular if dnsmasq is installed, then the lxcbr0 dnsmasq will fail, but /etc/init.d/lxc will ignore that. That makes future container starts hang mysteriously.
If something fails, make sure to clean up (remove lxcbr0) and return an error.
Changed in lxc (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
This bug was fixed in the package lxc - 0.7.5-3ubuntu17
---------------
lxc (0.7.5-3ubuntu17) precise; urgency=low
[ Serge Hallyn ] check-caps. patch: exit early and with a clear error message
* 0032-start-
if lxc-start is run with insufficient permissions. (LP: #925520)
* debian/lxc.init: if there is a failure during lxc network setup, clean
up and exit. (LP: #925511)
[ Stéphane Graber ] template- multiarch. patch: Add support for building
* 0033-ubuntu-
containers using qemu-user-static, using multi-arch to install some
packages of the host architecture so the container boots and works.
* Add qemu-user-static as a Suggest of lxc.
-- Stephane Graber <email address hidden> Thu, 02 Feb 2012 19:06:19 -0500