Setup always require clean state
vtrbtf opened this issue · comments
After executing the setup command, I've notice that the script always require a clean state ( Without Jessie image).
$ curl https://raw.githubusercontent.com/pixelated/puppet-pixelated/master/vagrant_platform.sh > vagrant_platform.sh; /bin/sh ./vagrant_platform.sh
...
...
...
Bringing machine 'jessie' up with 'virtualbox' provider...
==> jessie: Importing base box 'LEAP/jessie'...
==> jessie: Matching MAC address for NAT networking...
==> jessie: Checking if box 'LEAP/jessie' is up to date...
A VirtualBox machine with the name 'jessie' already exists.
Please use another name or delete the machine with the existing
name, and try again.
VM must be running to open SSH connection. Run `vagrant up`
to start the virtual machine.
@vtrbtf i ran into this myself. But i suspect the following problem: If you started a vagrant node with vagrant_platform.sh
, and either remove the 'leap_platform' folder, or run the same script in a different location, vagrant tries to start a second VM using the same name.
vagrant global-status --prune
shows all current vagrant VMs.
Please make sure to either vagrant destroy
your old box before starting a new one.
If you removed the leap_platform
folder already, i didn't find a way of destroying the now orphaned VM by vagrant itself, and you need to purge it from virtualbox.
Hope this helps!