Minikube: start/delete fails: open C:\Users\.minikube\machines\minikube\config.json: The system cannot find the file specified.

Created on 2 Oct 2019 · 12Comments · Source: kubernetes/minikube

I downloaded minikube in my windows 7 laptop. I installed it successfully. but when I try to run below command, it fails with below message. I tried minikube delete command also but it also fails. Not sure how to proceed . Please help,

$ minikube start

minikube v1.4.0 on Microsoft Windows 7 Enterprise Service Pack 1 6.1.7601 Build 7601
Retriable failure: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\.minikube\machines\minikube\config.jso
n: The system cannot find the file specified.
Retriable failure: Error loading existing host. Please try running [minikube delete], then run

[minikube start] again.: filestore "minikube": open C:\Users\.minikube\machines\minikube\config.jso
n: The system cannot find the file specified.

Retriable failure: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\.minikube\machines\minikube\config.jso
n: The system cannot find the file specified.
Retriable failure: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\.minikube\machines\minikube\config.jso
n: The system cannot find the file specified.
*
X Unable to start VM: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\.minikube\machines\minikube\config.js
on: The system cannot find the file specified.

help wanted kinbug lifecyclrotten owindows prioritbacklog

Source

vivekwpatil

👍1

All 12 comments

Looks like the same problem as here https://github.com/kubernetes/minikube/issues/5509. Try deleting C:\Users\.minikube\machines\minikube\ if minikube delete fails then run minikube start again.

woodcockjosh on 2 Oct 2019

👍1

Thanks. It starts after manually deleting that folder. I suppose minikube delete command should be taking care of this operation.

vivekwpatil on 2 Oct 2019

👍1

I think this can also occur if you run start minikube then cancel the command after the json file is created but before the machine instance is created.

woodcockjosh on 2 Oct 2019

Do you mind sharing what the error was when you ran minikube delete?

tstromberg on 3 Oct 2019

minikube appears to be doing a very weird thing with the path here (not surprising on Windows). Note that there is no actual home directory mentioned in the path.

tstromberg on 3 Oct 2019

👀1

when I try minikube delete it also tries to locate same config file and fails.

vivekwpatil on 6 Oct 2019

@vivekwpatil I am wondering are you running the minikube command while you are in C:\ drive ?

medyagh on 7 Oct 2019

On my side, everytime I call 'minikube delete' I also delete automatically %userprofile%/.minikube. It resolves a lot of weird behavior and doesn't create unwanted side effect, at least for me.

brainfull on 6 Nov 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 4 Feb 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 5 Mar 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 4 Apr 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.