touch-packages team mailing list archive

[Forest <1389864@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The lxc package installs dnsmasq configuration as
/etc/dnsmasq.d-available/lxc, and a symlink to it is created at
/etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
instance on systems running NetworkManager, because NetworkManager
starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d
instead.

This makes directing .lxc domain name lookups to the right place seem to
fail, which is how I noticed it.  I imagine it also leads to other
configurations not working as expected.

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

** Description changed:

  The lxc package installs dnsmasq configuration as
  /etc/dnsmasq.d-available/lxc, and a symlink to it is created at
- /etc/dnsmasq.d/lxc, but neither has any effect on systems running
- NetworkManager, because NetworkManager starts a dnsmasq instance that
- looks in /etc/NetworkManager/dnsmasq.d instead.
+ /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
+ instance on systems running NetworkManager, because NetworkManager
+ starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d
+ instead.
  
  This makes directing .lxc domain name lookups to the right place seem to
- fail, and probably leads to other thinks not seeming to work as
- expected.
+ fail, which is how I noticed it.  I imagine it also leads to other
+ configurations not working as expected.

-- 
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/1389864

Title:
  /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system

Status in “lxc” package in Ubuntu:
  New

Bug description:
  The lxc package installs dnsmasq configuration as
  /etc/dnsmasq.d-available/lxc, and a symlink to it is created at
  /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
  instance on systems running NetworkManager, because NetworkManager
  starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d
  instead.

  This makes directing .lxc domain name lookups to the right place seem
  to fail, which is how I noticed it.  I imagine it also leads to other
  configurations not working as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389864/+subscriptions