Vagrant Destroy Fails with ENOTEMPTY Error #12042
Description
Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use
HashiCorp Discuss: https://discuss.hashicorp.com/c/vagrant/24 Thank you!
When submitting a bug report, please provide the minimal configuration and required information necessary to reliably reproduce the issue. It
should include a basic Vagrantfile that only contains settings to reproduce the described behavior.
Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.
Vagrant version
2.2.13
Host operating system
Windows 10
Guest operating system
Windows Server 2016
Vagrantfile
https://github.com/clong/DetectionLab/blob/master/Vagrant/Vagrantfile
Debug output
https://gist.github.com/clong/af512ac5b04d2ecbe288b7d46470bd1c
Expected behavior
Vagrant should forcefully remove all vagrant instances and associated files
Actual behavior
Multiple "vagrant destroy" commands must be run in order to properly destroy and remove vagrant instances due to ENOTEMPTY errors
Steps to reproduce
- vagrant up
- wait for instances to be built
- vagrant destroy