I had the same problem and the previous answer didn’t work for me. I opened the VirtualBox GUI and saw that the virtual machine was running. I stopped it and then I executed “vagrant up“. All worked well.
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
I used this: config.vm.network :bridged , :mac => “080027XXXXXX” and got what I wanted. The docs are unclear on what the syntax for the options hash were, and there seemed to be no example on what this should look like. So, here it is! Bridged with a mac address (edited of course). This brings up … 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
The warning message occurs because your Docker storage configuration is using a “loopback device” — a virtual block device such as /dev/loop0 that is actually backed by a file on your filesystem. This was never meant as anything more than a quick hack to get Docker up and running quickly as a proof of concept. … Read more
you can use run: ‘always’ config.vm.provision :shell, path: “vagrant/bootstrap.sh”, run: ‘always’ This will make sure your command are executed every time your VM is starting (vagrant up or vagrant reload) If you need only certain commands to be always run, you can split your script config.vm.provision :shell, path: “vagrant/bootstrap1.sh” config.vm.provision :shell, path: “vagrant/bootstrap2.sh”, run: ‘always’ … Read more
Based on the output provided, the box has 2 network interfaces, 1 is the default NAT and the other private – ask you said. The reason why you are not able to access the web site hosted within the VM thru the private interface: it could be that host eth0 or wlan0 IP address is … Read more
In case of ssh port, Vagrant solves port collisions by itself: ==> ubuntu64: Fixed port collision for 22 => 2222. Now on port 2200. However, you still can create unavoidable collision by: Creating first vagrant env (it will get port 2222 for ssh) Suspend that env (vagrant suspend) Create second vagrant env (it will again … Read more