Open jaypipes opened 11 years ago
If you update the name server within the containers resolve.conf file to 10.0.3.1 does that get things working? If not, what about a direct address like 8.8.8.8? I think this may have to do with dnsmasq integration within network manager on the host. If you find one that works you can update the file in the base container at /var/lib/lxc/ubuntu_1204/rootfs/etc/resolved.conf. After that the newly created nodes will get the updated file and should be okay. Let me know what you find and I'll get an update applied for it. Cheers!
Yes, indeed, Chris, that got the ops node "unstuck" :) I manually set the first nameserver to 10.0.3.1 instead of 127.0.0.1 and that fixed things.
Now... how to get LXC base template that Vagabond uses to automatically set this when we do vagabond init? ;)
Okay, so I'm going to bet that it's a NetworkManager issue since I don't see that behavior and have NetworkManager dnsmasq disabled. I will likely provide a bit of logic in the vagabond cookbook for host configuration to inspect the host's resolv.conf
entries and make a best guess default, which the Vagabondfile can provide an override if required.
OK, cool, thanks Chris. Let me know if I can assist or if you want me to experiment with stuff.
Hi again Chris, I'm hoping you've run into something like this already and have a quick fix for me.
One of our cookbooks is using the Git Chef resource to download and install a repo from Github. Unfortunately, when the instance tries to execute chef-client, it fails while unable to reach github.com:
Is there some special sauce I need to put in my Vagabondfile to get external routing working properly? Here is my Vagabondfile, for reference. Thanks in advance for any insights...
BTW, really enjoying working with Vagabond. It's so much nicer than waiting for Vagrant and Virtualbox! :)