Trying to use Vagrant with VirtualBox on a Mac

[Paul Gureghian]

I had 'vagrant up' working and the vm was in virtualbox. the  next morning I ran 'vagrant up' again and I started getting errors like these. do I have to run 'vagrant up' in the terminal everytime, or just start the vm manually in virtualbox ? 

also, I havent been able to remove the UUID. should I remove the UUID or edit homestead.yaml so vagrant doesnt try to create a new vm ? 

thanks . 

[Alvaro Miranda Aguilera]

vagrant is trying to create the disk but virtualbox thinks already exists.

this may happen . if you delete boxes outside vagrant.

run vagrant destroy

open virtualbox, delete the VM

on virtualbox go to media manager, delete the disks you see there

this will give you a clean starting point.

alvaro

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2a7a97bd-1ea5-4aab-8cca-39abf1136e22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Paul Gureghian]

I uninstalled and reinstalled Virtual Box and Vagrant, 

 

Ran the provision script and I have a Homestead vm. 

The problem is the next day when I start everything again.

My choices as I see them are :  

1. Destroy vm then 'Vagrant up'  each day

2. Start Homestead vm in VirtualBox GUI

3.Do :  vagrant halt  homestead  ,   vagrant up homestead

On Saturday, July 20, 2019 at 9:28:32 AM UTC-7, Alvaro Miranda Aguilera wrote:

vagrant is trying to create the disk but virtualbox thinks already exists.

this may happen . if you delete boxes outside vagrant.

run vagrant destroy

open virtualbox, delete the VM

on virtualbox go to media manager, delete the disks you see there

this will give you a clean starting point.

alvaro

On Mon, Jul 15, 2019 at 12:24 AM Paul Gureghian <paulgu...@gmail.com> wrote:

I had 'vagrant up' working and the vm was in virtualbox. the  next morning I ran 'vagrant up' again and I started getting errors like these. do I have to run 'vagrant up' in the terminal everytime, or just start the vm manually in virtualbox ? 

also, I havent been able to remove the UUID. should I remove the UUID or edit homestead.yaml so vagrant doesnt try to create a new vm ? 

thanks . 

--
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 vagra...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2a7a97bd-1ea5-4aab-8cca-39abf1136e22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro