[Bug 925511] Re: lxc init script should fail when it ... failed
Serge Hallyn
925511 at bugs.launchpad.net
Tue Feb 7 15:49:48 UTC 2012
@Ritesh,
the dnsmasq for the lxc bridge explicitly binds only lxcbr0. So if that
fails, then your other dnsmasq has already bound all interfaces.
If /etc/init.d/lxc fails to start now, then lxcbr0 never had dhcp
before. If you're not using lxcbr0 for your containers, then you can
simply set USE_LXC_BRIDGE="false" in /etc/default/lxc.
If do want to use lxcbr0, then you should change your other dnsmasq to
not bind all interfaces.
A third alternative, I suppose, would be that you want to use lxcbr0 but
your statically assign addresses to your containers. We could add a
USE_LXC_BRIDGE_DNSMASQ variable to /etc/default/lxc to support that use
case. If that is what you want, please open a new bug against lxc and
I'll add it.
--
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/925511
Title:
lxc init script should fail when it ... failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925511/+subscriptions
More information about the Ubuntu-server-bugs
mailing list