network connectivity inside boot2docker machine about dvm HOT 16 CLOSED

This can be closed. I had vboxnet0 host-only networking inside Virtual Box. Once I removed that, I have no problems with network connectivity.

Sorry for the noise.

from dvm.

Oh excellent news!

from dvm.

I have the exact same problem and I don't understand the solution. I setup dvm using exactly the commands listed in the readme.

I feel like "dvm up" should give a completely functional vm without any further manual tweaking, but in the mean time, what is the workaround?

from dvm.

I added nameserver 8.8.8.8 to /etc/resolv.conf in the vm and things are working now.

from dvm.

Adding nameserver 8.8.8.8 to /etc/resolv.conf doesn't seem to work for me. I'm seeing the same issue.

from dvm.

Using VirtualBox 4.6.3. Adding nameserver 8.8.8.8 is not a solution for me either.

from dvm.

Applied 35ae30c which fixed this for me

from dvm.

👍 applying the patch mentioned by @wietsevenema fixed this issue for me as well. Thanks!

from dvm.

I'd rather have a complete solution here, but I suspect the DNS resolving issue is a problem with VirtualBox's networking under the hood. I've been trying to find a more thorough solution here, but in the meantime I'll merge in 35ae30c. Thanks everyone for your continued feedback!

from dvm.

Maybe set the nameserver to 10.0.2.3 ? https://forums.virtualbox.org/viewtopic.php?f=1&t=9410&start=0

from dvm.

The underlying issue might still be there.

This morning the VM was unable to connect again. The difference this time was that I had taken my laptop home in the evening and possibly used it on my home Wifi connection. Then I brought it back to work and used the usual wired connection and it was hosed. Sadly, I didn't do any forensics at this point and a dvm halt followed by dvm up fixed it for me.

from dvm.

@corporate-gadfly Do you have 35ae30c in your build? I installed it with:

$ brew reinstall --head dvm
$ dvm reload

from dvm.

I'm in the process of getting a release out the door with boot2docker 0.4.0 and the above commits in master. Then we should have a new baseline to troubleshoot any issues here.

from dvm.

Release 0.3.0 is out now https://github.com/fnichol/dvm/releases/tag/v0.3.0. Let's see if there are still issues now

from dvm.

@corporate-gadfly Can you reproduce this and see if you can ping 8.8.8.8? From what's in your original report, it's not clear if you're hitting a connectivity issue or a DNS issue.

from dvm.

I'm going to hope that this issue is effectively resolved as newer versions of VirtualBox, Vagrant, boot2docker-vagrant-box, and boot2docker have been since been released. If I'm incorrect, please open a new pull request & we'll re-evaluate the state of things. Thanks!

from dvm.