-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
delete: remove VBox.log: The process cannot access the file because it is being used by another process. #4286
Comments
Removing or moving directory ~/.minikube/machines/minikube helps to return back to initial state of minikube, state after installation. |
Interesting. I suspect than on Windows, you may need to run If that fixes it, we should just make that step automatic. |
I have the same problem and tried this:
and then
This seems to be show-stopper for me. :(
|
Hi
It is great to use minukube. Thank you.
But looks like sometimes minikube is not able to delete cluster on Windows 10 with VirtualBox. I think potential cause can be slow work of VirtualBox: file with logs are still in use when minikube is trying to clean up resource in file system.
Please find detail below. All steps to reproduce in attached txt file.
The exact command to reproduce the issue:
minikube delete
The full output of the command that failed:
C:\Windows\system32>minikube delete
x Deleting "minikube" from virtualbox ...
! Failed to delete cluster: remove C:\Users\Anton.minikube\machines\minikube\minikube\Logs\VBox.log: The process cannot access the file because it is being used by another process.
The output of the
minikube logs
command:C:\Windows\system32>minikube logs
! api load: filestore: open C:\Users\Anton.minikube\machines\minikube\config.json: The system cannot find the file specified.
The operating system version:
Microsoft Windows [Version 10.0.17763.475]
This issue looks like #4137 but I don't know shweta9651's previous commands.
Oracle VirtualBox Version 5.2.8 r121009 (Qt5.6.2)
minikube_crash_clean.txt
The text was updated successfully, but these errors were encountered: