Jacob,

This may be the same issue I had recently: 
https://groups.google.com/d/msg/vagrant-up/bHe04cJJMAE/hm49gqJIAgAJ

Is there a *.vmx.lck directory in 
/home/devJacob/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/4.0.0/ ?

If so, you have to delete it. It should not have been included by the 
creator of the Vagrant box.

If not, try setting "linked_clone = false" for your provider VM as a 
workaround so the VM is copied as opposed to linked.

On Thursday, November 2, 2017 at 5:22:28 PM UTC-7, Jacob Sherman wrote:
>
> here is a gist of the debug file
> https://gist.github.com/NYCJacob/e7c8ee74a4b380860e5759001abf9ed8
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/bd0c594b-859b-4289-a0f7-2312a3eec481%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to