Skip to content
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

Unable to stop VM: open config.json: The system cannot find the file specified. #5930

Closed
umathivagit opened this issue Nov 16, 2019 · 6 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. os/windows priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@umathivagit
Copy link

minikube stop

X Unable to stop VM: open C:\Users\Uday.minikube\machines\minikube\config.json: The system cannot find the
file specified.
*

Windows 10

@RA489
Copy link

RA489 commented Nov 19, 2019

@umathivagit can you please copy paste exact command and environments you are using?

@brainfull
Copy link

brainfull commented Nov 19, 2019

unfortunately it happens too often, the only reliable fix I found for now is to delete the whole %userprofile%/.minikube directory

this often happens because of retriable failure : see #5884 #5941

also add comments in #5072 for better windows support

@tstromberg tstromberg changed the title Unable to stop or delete minikube Unable to stop VM: open config.json: The system cannot find the file specified. Nov 20, 2019
@tstromberg tstromberg added os/windows priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Nov 20, 2019
@tstromberg
Copy link
Contributor

If config.json is missing, we should be erroring in such a way that says something like:

exit.WithCode(exit.Conflict, "Unable to stop cluster, as it does not exist")

I'm a little confused, because StopHost used to be able to catch this error appropriately.

@tstromberg tstromberg removed the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Nov 20, 2019
@umathivagit
Copy link
Author

unfortunately it happens too often, the only reliable fix I found for now is to delete the whole %userprofile%/.minikube directory

this often happens because of retriable failure : see #5884 #5941

also add comments in #5072 for better windows support

Yes that worked...thanks..

@tstromberg tstromberg added the kind/bug Categorizes issue or PR as related to a bug. label Dec 19, 2019
@tstromberg
Copy link
Contributor

Do you mind checking to see if this is still the case in minikube v1.7.0?

@tstromberg
Copy link
Contributor

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. os/windows priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants