Vagrant: Force destroy vagrant instance that "was not found configured for this Vagrant environment"

Created on 1 Oct 2014 · 3Comments · Source: hashicorp/vagrant

I guess i don't really care if it was found in the environment, i just want to destroy the box because it was made and is in the global status. Worse is that the box is running and i can't halt it or anything. Vagrant knows what the ID is (because it is in global-status) so it should be pretty simple.

This becomes a problem when you are actively working, do a vagrant up, change the name of the vm / add another vm and do another vagrant up. You end up with an orphan that can not be killed (unless i manually remove all reference too it and then drop it from the VM Manager)

core enhancement

Source

gwagner

Most helpful comment

Hi there,

Thank you for opening an issue. In the next version of Vagrant, all the "regular" vagrant commands accept a global status ID in addition to a VM name, so you will be able to use vagrant destroy ID-FROM-GLOBAL-STATUS. Additionally, the global-status is a cache, not a true representation of the current state. You many need to run global-status --prune. Thanks! 😄

sethvargo on 30 May 2016

👍4

All 3 comments

Hi there,

sethvargo on 30 May 2016

👍4

Updated from 1.8.5 to 2.1.2 and this is the response:

==> You need a `setup.yml` file

franz-josef-kaiser on 29 Jul 2018

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.