Came across a similar issue, one thing I don’t see mentioned here is you need to start docker to listen to both the network and a unix socket. All regular docker (command-line) commands on the host assume the socket. sudo docker -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock -d & will start docker listening to any ip address … Read more
Vagrant’s boot2docker keeps boot2docker’s ssh username and password. SSH into VM $ boot2docker ssh Boot2Docker auto logs in using the generated SSH key, but if you want to SSH into the machine manually (or you’re not using a boot2docker managed VM), the credentials are: user: docker pass: tcuser https://github.com/boot2docker/boot2docker#ssh-into-vm The port is forwarded from the … Read more
2021 Update: In 2021 no need for unique Id or being nfs, just list your synced folders: config.vm.synced_folder “.”, “/vagrant/Sites” config.vm.synced_folder “../Code”, “/vagrant/Code” Original answer: I just needed to set a unique ID for each mount, and then reload the vagrant box. # Use NFS for the shared folder config.vm.synced_folder “.”, “/vagrant/Sites”, id: “sites”, # … Read more
I ran into this problem as well. The trick is to download the modules using a vagrant shell command before the puppet provisioner runs. config.vm.provision :shell do |shell| shell.inline = “mkdir -p /etc/puppet/modules; puppet module install puppetlabs/nodejs; puppet module install puppetlabs/apache” end config.vm.provision :puppet do |puppet| puppet.manifests_path = “puppet/manifests” puppet.manifest_file = “site.pp” end Order is … Read more
If you are using Vagrant + VirtualBox + Ubuntu, you might want to add the following block to your VagrantFile: config.vm.provider “virtualbox” do |v| v.customize [“modifyvm”, :id, “–natdnshostresolver1”, “on”] v.customize [“modifyvm”, :id, “–natdnsproxy1”, “on”] end If you are using ubuntu, and you think your firewall is on, here’s how you turn off the firewall: sudo … Read more
I found the “issue” started to happen after VirtualBox 6.1.26. The way to solve is creating a new file at /etc/vbox/networks.conf on your macOS with content * 10.0.0.0/8 192.168.0.0/16 * 2001::/64 Make sure including the asterisks *. Then the issue should be gone. Regarding the networks.conf content, it can be found at https://www.virtualbox.org/manual/ch06.html#network_hostonly
EngineerCoder’s answer only applies if you’re using CoreOS. I’ve run into problems if the VirtualBox Extensions pack version differs from the version of VirtualBox. Also, install the Vagrant VirtualBox guest plugin: vagrant plugin install vagrant-vbguest And make sure to update the plugin when you update Virtualbox and the extension pack: vagrant plugin update vagrant-vbguest
The solution is to use vagrant-hostsupdater vagrant plugin install vagrant-hostsupdater This plugin adds an entry to your /etc/hosts file on the host system. On up and reload commands, it tries to add the information, if its not already existant in your hosts file. If it needs to be added, you will be asked for an … Read more
in your Vagrantfile, you should add config.vm.network “public_network”, bridge: “Intel(R) 82579LM Gigabit Network Connection” Then it should make vagrant happy (actually its more VirtualBox that is getting happy in this case) and select the correct network adapter for the VM