Closed MiroslawKmiec closed 5 years ago
Hi @MirekKmiec - Do you have a debug log showing this behavior with vagrant halt --debug
? Generally, Vagrant shouldn't be deleting any folders. When you run the vagrant halt
command, Vagrant simply calls out to your guests capability definition for halt, which in most linux case is just running the command shutdown
on the guest. Maybe the Vagrant box you are using has a trigger to delete the current working dir, but I doubt it :thinking: Anyway without a debug log it is hard to know what happened so giving us that with the delete behavior would be a good start. Thanks!
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks!
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.
Vagrant version
2.2.4
Host operating system
Win 10 Pro 64-bit, cpu i7, 16GB ram, ssd sata III
Guest operating system
Debian stretch
Vagrantfile
Debug output
Expected behavior
"vagrant halt" should close normaly.
Actual behavior
Randomly after "vagrant halt" whole dierctory is deleted (including Vagrantfile, .vagrant, and data). Virtual boxes and shared folders remains. I observed that twice. On second monitor I had opened file manager so I think that is problem with vagrant (hardware problem I think is not issue). Antyvirus scan with Bitdefender and Malwarebytes nothing found. SSD SMART informations are ok. With new version 2.2.5 not tested yet.