Try doing this... You should see a vagrant box that is listed that is linked to your composer/vendor...
vagrant global-status
Example Output:
λ vagrant global-status
id name provider state directory
-----------------------------------------------------------------------------------------------------
1ace413 default virtualbox running C:/Users/Tyler/AppData/Roaming/Composer/vendor/laravel/homestead
Then go ahead and run:
vagrant provision {ID}
Example input:
vagrant provision 1ace413
ID being the id of the vagrant instance in the above step.
Howdy!
@Craytor thanks for the answer. Had the same issue. Does this mean there's some bug in the Homestead 2.0 code or is there something else that could be involved that Renato and I both did? Just curious.
@weerd Sorry for the late response! I honestly don't know, I've ran into the same issue and I've tried multiple solutions, and this is the only fix that I have found.
Sorry to bring this old thread back alive.
I'm still having issues after trying the solutions in this thread.
For some reason my homestead machine has disappeared. The homestead folder with .vbox files and everything else is found in my user folder in the folder VirtualBox VMs.
So that looks fine.
When i do "vagrant global-status" it says there is no active Vagrant environments. And thats pretty wierd..
So it seems like Vagrant has forgotten my box.
I can find information about it in .composer/vendor/laravel/homestead
Ive tried cd'ing in to that folder to run vagrant reload --provision, or vagrant up.
Nothing works, i get "==> default: VM not created. Moving on..."
So, the machine and its .vmdk files are still there. How do get Vagrant to find my machine again?
