touch-packages team mailing list archive

[Forest <1389954@xxxxxxxxxxxxxxxxxx>]

Okay, I've written up a short README.Debian describing the necessary
changes to /etc/default/lxc-net and the dnsmasq config file. I don't
remember what steps are necessary to make the domain names accessible,
though, and I'd like to include those steps in the readme.

Do I have to restart the lxc-net service? (And is that service called
the same thing regardless of whether sysv init, upstart, or systemd is
in use?)

Do I have to restart NetworkManager?

Do I have to restart any already-running containers?

-- 
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:
  Confirmed

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