Laravel Homestead: "VM not created .. moving on"

Question

I did a global installation of the Laravel family, edited my ~/.homestead/Homestead.yaml file, and deployed the VM using homestead up . Everything worked fine, but then I needed to add another site. I edited Homestead.yaml to add a new project, tried to run homestead provision to apply the changes to the virtual machine. The only thing that produces:

 ==> default: VM not created. Moving on... 

I interpret this as the VM is not working, but it is. The only thing that works here is homestead destroy , followed by homestead up , but which (by its nature) shares the state of the saved virtual machine. I, although these roaming teams were applicable to the estate, but vagrant suspend && vagrant up --provision does not help.

So ... How do I apply a new configuration to an existing Homestead virtual machine?

Answer 1

I found the answer on Laracasts . Copied right from there:

Try this ... You will see a widget box that is listed that is associated with your composer / provider ...

 vagrant global-status 

Result:

 $ vagrant global-status id name provider state directory ----------------------------------------------------------------------------------------------------- 1ace413 default virtualbox running (...)/laravel/homestead 

Then run:

 vagrant provision {ID} 

Input Example:

 vagrant provision 1ace413 

The identifier that is the identifier of the roaming instance in the previous step.

Then you will be well!

Answer 2

I recently changed my laptop from 32-bit to 64-bit and should again install and configure my Homestead.

After setting everything that I run under the command

 vagrant reload --provision 

and I get the same feedback that

 ==> default: VM not created. Moving on... 

After that, I try this command and everything works well.

 vagrant up 

I think that for the first start of Homestead, there is no need to restart -provision.

Answer 3

You can run vagrant provision to update websites at home. However, you need to find where the Vagrantfile for the Homestead VM is located. If you made a global installation, it should be in the directory .composer/vendor/laravel/homestead/ . You need to go to this directory

 cd ~/.composer/vendor/laravel/homestead 

Then you need to specify VM

 vagrant provision 

Your estate cell should reflect the changes in the Homestead.yml file.

Edit: I'm not on my mac right now, so the directory path is a hunch about what I remember, since this was the last time I provided my mailbox, so please keep this in mind, but I'm very sure the path must be correct.