Geek Answers Handbook

A tramp falls depending on the physical network

I have a virtual machine that I control with using Vagrant. Upon initialization, I get some updates for the system (Ubuntu) with apt-get, install Node.js with nvm, and then run npm installfor various modules. Strange things happen now:

If I try to create and provide a virtual machine on physical network A (in one place), the initialization will fail. Either the creation is already failing, and Wagrant tells me that the machine has gone into an invalid state, or the VM will work when npm starts to do its job.

If I try to do the same on physical network B (elsewhere), everything will be fine.

As soon as the difference between the two places (I can think of) is a physical network, I wonder how this can happen. I tried this with two different MacBooks, one of which was running Mavericks, and the other was Mountain Lion. The effect occurs on both, and when using different versions of Vagrant / VirtualBox, so, apparently, this is actually a problem of the environment.

Any idea what might cause such problems?

+4
source share
1 answer

I know this thread is a bit older, but I have the same problem and I found a solution.

Here is the official problem and solution https://github.com/mitchellh/vagrant/issues/2786

, "NAT Networking" DNS-. npm install .

, github:

config.vm.provider :virtualbox do |vb|
    vb.customize ['modifyvm', :id, '--natdnshostresolver1', 'on']
end

, .

+8

More articles:


All Articles