minikube: config.json: no such file or directory

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

Minikube version (use minikube version): v0.15.0

Environment:

OS (e.g. from /etc/os-release): macOS 10.12
VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): File doesn’t exist
Docker version (e.g. docker -v): Docker version 1.12.6, build 78d1802
Install tools:
Others:

What happened:

$ minikube start
Starting local Kubernetes cluster...
E0118 13:29:31.839028    3722 start.go:96] Error starting host: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: open /Users/galkinrost/.minikube/machines/minikube/config.json: no such file or directory.

 Retrying.
E0118 13:29:31.839598    3722 start.go:102] Error starting host:  Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: open /Users/galkinrost/.minikube/machines/minikube/config.json: no such file or directory

What you expected to happen: Minikude successful starts

How to reproduce it (as minimally and precisely as possible): I followed the steps described in this tutorial https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/

Anything else do we need to know:

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 11
Comments: 33 (4 by maintainers)

Most upvoted comments

It’s hard to guarantee in place upgrades from 0.6 to 0.15, so that’s most likely not going to work. Your best option is to delete the minikube folder ‘rm -from ~/.minikube’ and perform a minikube start

+25

r2d4 on Feb 22, 2017

Same problem with minikube delete. yes, @r2d4 was right. just “rm -rf ~/.minikube/”. thank you, @r2d4 !

+15

tomtsang on Aug 7, 2017

I was able to get past this error by deleting my ~/.minikube directory (OS X 10.11.6). Then minikube start had to download the ISO again.

AdamCanady on Aug 5, 2017

I use Hyper-V driver. What worked for me was:

open Hyper-V manager
delete all the minikube machines from there
delete the folder .minikube
run minikube start --vm-driver=hyperv

if you skip step 1 and 2, you’ll probably won’t be able to delete the folder .minikube (for me, it was under C:\Users\user)

Hope this works for you all, folks

ghost on Jan 25, 2019

I had the same problem. I deleted the ./minikube/machines/minikube directory and I could start minikube again.

aczelcs on May 2, 2018

Got the same error as @KJX16

$ minikube delete
Deleting local Kubernetes cluster...
Errors occurred deleting machine:  Error deleting host: minikube: open /Users/galkinrost/.minikube/machines/minikube/config.json: no such file or directory

galkinrost on Jan 20, 2017

Can you try a minikube delete and then another minikube start?

r2d4 on Jan 19, 2017

minikube version: v0.25.2 windows 10

after a reboot minikube start --vm-driver=hyperv would not work. minkube delete complaint a missing config file (as above).

workaround: remove remove hyper-v virtual machine and remove .minikube folder; rerun minikube --vm-driver=hyperv as admin.

cons0l3 on Apr 2, 2018

minikube version: v0.28.0 using Windows Server 2016 using Hyper-V

Deleted ./minikube directory, but still had trouble restarting minikube. Sometimes had trouble stopping or deleting minikube. Had to manually delete using Hyper-V manager. Reran minikube with --vm-driver=hyperv --hyperv-virtual-switch=(my switch) --logtostderr -v5 No errors showed up, but it began to hang at “Starting cluster components” Output below:

Starting cluster components… I0629 09:34:16.895277 8000 ssh_runner.go:80] Run with output: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable–etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable–data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable–etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable–etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=Fil eAvailable–etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable–etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI

paulinalei on Jun 29, 2018

creating empty configure.json doesnt work. just delete .minishift folder under user directory and it will work

imranrazakhan on Jun 5, 2017