-----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 26/06/15 20:41, Christopher Townsend wrote: > Hey Serge, > > Yes, I can confirm that setting "LXC_DHCP_CONFILE=/dev/null" does > indeed make it work. > > Thanks! > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJVmZu1AAoJEBXN2mrhkTWiX0YP/jN8smIOJxSj5A+aXsNhNvAL P+awNJoTV+qh+CEAaYQkNv+A+2pDbPlggJeJl24jHIsBOURcPM32ziqP9NyOFoQ+ +ryeK9pRLLE2TrrFc7JguM8DYSKlHRzBldTtCzU5Lfiom2PJm3iB96uAdNNsLU5J dLjicEBhQjs/PnM5x+tonWinGbpyJYJ0Kh9gRg9VG7aG571oyFn56Tj9PxEhZV7c 2rpVomrm2FL+C+9ozRJHcwj+Wv76IeUXSEk1nyjEbr0U+F5AvzdU/wXfydHxQlv/ igB8RivZozaWp2Xz62lnHaRRBA7QSeuCu08vngsKqBmP5HURgejzhOGfmBhnt7ZK HI35CNXAqAL/RFDiSbSXzzdQOEHN30Ferr0hZr57UxHbOgtFZV+c57wBciEU/gRv k6tkC/eJ7OuzrPrfK4cxSli2aeQEIDKmesQTrFP63pD11QwSXgBhRousArLqljgE 13RRwDkPXLYF9iKXem5z9qXAAxocmjYqmrQhjq51VUqOM6Svk0vSuZEk2K7TuS2L tsYNRZDUwIRYpJfzKKnQK1+flh7Y5WorcxWbNfMDBDhtLhUNoCvg4yH5+tI7x7eF oZAVBXo0mpdJkrmKGjhQkMunssIujsY4Nbc22guv9LWh/OpXteYFAmQRVmZcPHYO c5soqxgCzoOJNm3KBf2s =Dj/i -----END PGP SIGNATURE----- -- 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: Confirmed Status in lxc package in Ubuntu: Fix Committed Bug description: The lxc-net systemd service calls /usr/lib/x86_64-linux-gnu/lxc/lxc- net start. This causes dnsmasq -s lxc -S /lxc/ -u lxc-dnsmasq --strict-order --bind- interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen- address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp- leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative to be run. With dnsmasq-base 2.72-3.1 this works fine. With 2.73-1 it fails with: dnsmasq: cannot read /etc/dnsmasq.conf: No such file or directory unless one creates /etc/dnsmasq.conf, after which it succeeds. Is this a change in the handling of --conf-file=- ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1468611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
