← Back to team overview

touch-packages team mailing list archive

[Bug 1468611] [NEW] dnsmasq fails to start in lxc-net

 

Public bug reported:

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=- ?

** Affects: dnsmasq (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: lxc (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1468611

Title:
  dnsmasq fails to start in lxc-net

Status in dnsmasq package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New

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


Follow ups

References