Hi,
personally in 15.10 I have
# Tell any system-wide dnsmasq instance to make sure to bind to interfaces
# instead of listening on 0.0.0.0
# WARNING: changes to this file will get lost if lxc is removed.
bind-interfaces
except-interface=lxcbr0
server=/lxc/10.0.3.1
in /etc/dnsmaq.d/lxc
and it d
Tried to follow the documentation on Ubuntu Server 15.04 with no luck. I
have activated LXC_DOMAIN="lxc" in /etc/default/lxc-net, then created
/etc/dnsmasq.conf and added server=/lxc/10.0.3.1 (there is no
NetworkManager installed). Tried to reboot, but still getting "ping:
unknown host container.l
Here's a first attempt:
https://github.com/lxc/lxc-pkg-ubuntu/pull/2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover an
Yes, lxc-net is called lxc-net in all init systems where the job exists
(syv, upstart, systemd)
Both lxc-net and network-manager need to be restarted (unless network-
manager is smart and uses inotify to look for updates).
I don't believe containers would need to be restarted.
--
You received t
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-n
I think dpm-vivid would be the right one.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
To manage notific
Which branch?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
To manage notifications about this bug go to:
Yes, you might add debian/README.Debian there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
To manage no
Sure. Is this the right place?
https://github.com/lxc/lxc-pkg-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover an
Would you care to upload a patch to edit README.Debian with that
information?
Note that the non-network-manager version of this is currently commented
in https://help.ubuntu.com/14.04/serverguide/lxc.html .
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
Thanks for taking an interest in the issue.
Since I filed this specifically against lxc in Ubuntu, wouldn't it make
sense to start by documenting the necessary config changes (including
NetworkManager's dnsmasq config, since it is part of Ubuntu by default)
in /usr/share/doc/lxc/README?
--
You r
This has been discussed before. I definately want to make things work
as cleanly as possible out of the box. There are a few problems with
doing htis though, 1) networkmanager isn't the only place we'd need to
do this (most "serious" lxc hosts probably don't run networkmanager), 2)
if we do this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
T
13 matches
Mail list logo
