I\'m using Vagrant for my environment and I\'ve got a little issue:
$vagrant up
Bringing machine \'default\' up with \'virtualbox\' provider...
==> defau
If you're using OS X and used the standard install, Delete vagrant's old curl and it should now work
sudo rm /opt/vagrant/embedded/bin/curl
When you do vagrant init , it replaces the vagrant file in your repo and can give you that error. So I would suggest you copy the original vagrant file from remote or a backup vagrant file and try vagrant up after that.
I came across same issue and I just copied the vagrant file from my remote repo and replaced the vagrant file I was trying to run. This synced the configurations in the vagrant file with the VM.
i experience this error too. I think it was because I failed to supply a box_url..
vagrant init precise64 http://files.vagrantup.com/precise64.box
In case, you added a box and started downloading it but interrupted that download, go to ~/.vagrant.d/tmp/
and delete the partial download file, then try again.
Please run this in your terminal:
$ vagrant box list
You will see something like laravel/homestead(virtualbox,x.x.x)
Next locate your Vagrantfile
and locate the line that says
config.vm.box = "box"
replace box
with the box name when you run vagrant box list
.
Check the following entry in your Vagrantfile
Every Vagrant development environment requires a box.
You can search for boxes at https://vagrantcloud.com/search.
config.vm.box = "base"
This is the default file setting which is created with vagrant init command. But what you need to do is do initialise vagrant environment with an OS box. For instance $vagrant init centos/7. And the Vagrantfile will look something like this:
Every Vagrant development environment requires a box.
You can search for boxes at https://vagrantcloud.com/search.
config.vm.box = "centos/7"
This will resolve the error of not found base when doing a vagrant up.