** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
Statu
This bug was fixed in the package dnsmasq - 2.74-1
---
dnsmasq (2.74-1) unstable; urgency=low
* New upstream. (LP: #1468611)
-- Simon Kelley Wed, 15 Jul 2015 21:54:11 +
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Fix Released
--
You received this
** Branch linked: lp:ubuntu/wily-proposed/dnsmasq
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
Status in dnsmasq package in
** Branch linked: lp:debian/dnsmasq
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
Status in dnsmasq package in Ubuntu:
Con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The underlying problem is that 2.73 accidentally change the meaning of
dnsmasq --conf-file
from "don't read any conf-file" to "read the default conf-file".
This is a bug, not a feature, and I've just committed a fix to git.
Cheers,
Simon.
On
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
Status i
Thanks, workaround posted to lxc-devel mailing list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsmasq fails to start in lxc-net
Status in dnsmasq package
Hey Serge,
Yes, I can confirm that setting "LXC_DHCP_CONFILE=/dev/null" does indeed
make it work.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1468611
Title:
dnsma
(indeed that seems to fix it here, @townsend could you try? Just set
LXC_DHCP_CONFILE=/dev/null
in /usr/lib/x86_64-linux-gnu/lxc/lxc-net
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.
If it comes to it, I suspect we could pass --conf-file=/dev/null and
have it work.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launc
I'm hitting this too. When the lxcbr0 device is not available, my
unpriv'd containers will not start due to not being able to set up the
network.
If I just touch /etc/dnsmasq.conf, then it all works as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/b
13 matches
Mail list logo
