touch-packages team mailing list archive

[Forest <1389954@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The lxc package on ubuntu does almost nothing to help a user enable DNS
resolution for containers via dnsmaq, let alone discover that it is
possible. How about enabling it by default? I think all it would take is
adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/
and uncommenting LXC_DOMAIN="lxc" in /etc/default/lxc-net.

Even if there's a good reason not to enable this by default, shouldn't
it at least be clearly documented someplace obvious instead of buried in
a system config file with a misleading comment that mentions the wrong
dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-
net does nothing on ubuntu desktop systems, because ubuntu's
NetworkManager starts dnsmasq with a special config directory.)

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

** Description changed:

  The lxc package on ubuntu does almost nothing to help a user enable DNS
  resolution for containers via dnsmaq, let alone discover that it is
  possible. How about enabling it by default? I think all it would take is
  adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/
  and uncommenting LXC_DOMAIN="lxc" in /etc/default/lxc-net.
  
  Even if there's a good reason not to enable this by default, shouldn't
  it at least be clearly documented someplace obvious instead of buried in
  a system config file with a misleading comment that mentions the wrong
- dnsconf file to edit? (The dnsconf file path currently mentioned in
+ dnsmasq file to edit? (The dnsconf file path currently mentioned in
  /etc/default/lxc-net does nothing on ubuntu desktop systems, because
  NetworkManager starts dnsconf with a special config directory.)

** Description changed:

  The lxc package on ubuntu does almost nothing to help a user enable DNS
  resolution for containers via dnsmaq, let alone discover that it is
  possible. How about enabling it by default? I think all it would take is
  adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/
  and uncommenting LXC_DOMAIN="lxc" in /etc/default/lxc-net.
  
  Even if there's a good reason not to enable this by default, shouldn't
  it at least be clearly documented someplace obvious instead of buried in
  a system config file with a misleading comment that mentions the wrong
- dnsmasq file to edit? (The dnsconf file path currently mentioned in
- /etc/default/lxc-net does nothing on ubuntu desktop systems, because
- NetworkManager starts dnsconf with a special config directory.)
+ dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-
+ net does nothing on ubuntu desktop systems, because ubuntu's
+ NetworkManager starts dnsmasq with a special config directory.)

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

Title:
  Make .lxc domain name resolution easier to discover and enable

Status in “lxc” package in Ubuntu:
  New

Bug description:
  The lxc package on ubuntu does almost nothing to help a user enable
  DNS resolution for containers via dnsmaq, let alone discover that it
  is possible. How about enabling it by default? I think all it would
  take is adding server=/lxc/10.0.3.1 to a file in
  /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN="lxc" in
  /etc/default/lxc-net.

  Even if there's a good reason not to enable this by default, shouldn't
  it at least be clearly documented someplace obvious instead of buried
  in a system config file with a misleading comment that mentions the
  wrong dnsmasq file to edit? (The one currently mentioned by
  /etc/default/lxc-net does nothing on ubuntu desktop systems, because
  ubuntu's NetworkManager starts dnsmasq with a special config
  directory.)

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