A VirtualBox machine with the name 'homestead' already exists

Question

Since homestead 2.0 homestead laravel has not been working

I don\'t know why \'homestead init\' creates a Homestead.yaml file in mydirectory/.homestead and not in

Answer 1

None of this worked for me. I was using an old dev machine

I attempted:

1. vagrant global-status > destroy any by id which you don't need or match what is conflicting

2. open virtualbox and remove + delete files for any which you don't need or are conflicting

What worked:

• locate your ~/.vagrant/machines/ or ~/.vagrant.d/boxes folder. In my case, it contained the conflicting vm and also a bunch of old left over vm machines which steps 1 & 2 did not remove for some reason.

• after clearing these, everything worked fine again, finally!