Given comment #5, I am going to mark this 'wontfix', as its a clever
idea that seems like overkill.
If someone wants to write the patch to do this I won't be opposed.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member
** Changed in: lxc (Ubuntu)
Importance: Undecided = Wishlist
** 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/824167
Title:
The templates tweak dhclient.conf so that the container should send its
hostname. If you have dnsmasq running (i.e. if you are connecting your
clients to a libvirt bridge), and your host has 'nameserver
192.168.122.1' at the top, then you should be able to 'ssh
container.'.
Since lxc is not
Apparently that doesn't work. I modified the host's dhclient.conf to
add:
prepend domain-name-servers 192.168.122.1;
Such that /etc/resolv.conf now contains:
nameserver 192.168.122.1
nameserver 10.0.1.1
dnsmasq seems to be running:
1366 dnsmasq --strict-order --bind-interfaces
After a reboot, this is now working!
May I change the suggestion to use avahi to instead modify the host's
dhclient.conf as I done above instead? Or maybe you can come up with a
better way to do it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Quoting Sidnei da Silva (824...@bugs.launchpad.net):
After a reboot, this is now working!
May I change the suggestion to use avahi to instead modify the host's
dhclient.conf as I done above instead? Or maybe you can come up with a
better way to do it.
I'm afraid I know nothing about avahi.
Avahi is nothing more than a multicast-dns implementation. if avahi-
daemon is installed in the container and libnss-mdns (IIRC) in the host,
then the container will broadcast it's hostname through mdns and the
host would be able to resolve it. It might be overkill however,
specially since the
