Hot answers tagged

3

A few years later this thread is still the first result in Google, but running Docker+Vagrant (with VirtualBox) on Windows isn't a challenge anymore. You can easily run them both, as described here If for some reason you want to use Vagrant with VirtualBox as a provider you should update to VB 6.x - after that, you can run VirtualBox, Vagrant, and Docker at ...


2

eth0 is used by vagrant for nat configuration in order to establish portforwarding. eth1 private networks that you have configured should allow you to ping/nslookup from one node to another. You can use the following to customize the ip of the nat but I don't see why would you do that: config.vm.provider "virtualbox" do |vbx| vbx.customize ['modifyvm', :...


1

An alternative sintax to Dilson Rainov's answer, more ansible 2.x style (I think). In your inventory define the host as: vagrant-local: ansible_host: 192.168.33.10 ansible_user: vagrant ansible_ssh_private_key_file: .vagrant/machines/default/virtualbox/private_key UserKnownHostsFile: /dev/null StrictHostKeyChecking: no ...


Only top voted, non community-wiki answers of a minimum length are eligible