Hi Stéphane,
assigned this to you just to get your input, as I imagine you have a
perfect solution right offhand.
On my servers, /etc/hosts lists the hostname as public ip address, and
there is no problem. On my laptops with network-manager, when I start
a container and 'ping <laptop-name>', it pings 127.0.1.1. Adding
--no-hosts to the dnsmasq line is imo wrong, but is there anything else
we can to handle the 127.0.1.1 case?
I suppose we could use -E with a one-line hosts file which lists the
hostname as 10.0.3.1. Or use -S.
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
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/1326536
Title:
libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in
odd resolution behaviour on the VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
