My Vagrant 1.7.2 machine bugged out and when I tried to `vagrant up` it spawned a new box instead of bringing up my existing machine.
Naturally this was a problem because I had made some manual changes to the config that I hadn't had a chance to persist to my puppet config files yet.
To fix the problem I found used the command `VBoxManage list vms` in the directory where my Vagrantfile is. This provided me a list of the machine images it could find.
I then went and edited the file at .vagrant/machines/default/virtualbox/id and replaced the UUID that was in there with the one that the VBoxManage command had output.
Now when I run 'vagrant up' it spins up the correct VM. Happy days.
Naturally this was a problem because I had made some manual changes to the config that I hadn't had a chance to persist to my puppet config files yet.
To fix the problem I found used the command `VBoxManage list vms` in the directory where my Vagrantfile is. This provided me a list of the machine images it could find.
I then went and edited the file at .vagrant/machines/default/virtualbox/id and replaced the UUID that was in there with the one that the VBoxManage command had output.
Now when I run 'vagrant up' it spins up the correct VM. Happy days.
Comments
Post a Comment