Minikube: none: can't delete cluster: output: sudo: kubeadm: command not found

[staticdev]

The exact command to reproduce the issue:

minikube start --vm-driver=none
minikube delete

The full output of the command that failed:

🔄 Uninstalling Kubernetes v1.15.0 using kubeadm ...
Failed to delete cluster: kubeadm reset: sudo kubeadm reset --force

: running command: sudo kubeadm reset --force
output: sudo: kubeadm: command not found
: running command: sudo kubeadm reset --force
.: exit status 1
🔥 Deleting "minikube" from none ...

💣 Failed to delete cluster: exit status 5

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new

The output of the minikube logs command:

E0626 21:08:30.645515   29069 logs.go:155] Failed to list containers for "kube-apiserver": running command: docker ps -a --filter="name=kube-apiserver" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-apiserver%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-apiserver" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.679709   29069 logs.go:155] Failed to list containers for "coredns": running command: docker ps -a --filter="name=coredns" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22coredns%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=coredns" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.714497   29069 logs.go:155] Failed to list containers for "kube-scheduler": running command: docker ps -a --filter="name=kube-scheduler" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-scheduler%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-scheduler" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.748430   29069 logs.go:155] Failed to list containers for "kube-proxy": running command: docker ps -a --filter="name=kube-proxy" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-proxy%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-proxy" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.782817   29069 logs.go:155] Failed to list containers for "kube-addon-manager": running command: docker ps -a --filter="name=kube-addon-manager" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-addon-manager%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-addon-manager" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.816555   29069 logs.go:155] Failed to list containers for "kubernetes-dashboard": running command: docker ps -a --filter="name=kubernetes-dashboard" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kubernetes-dashboard%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kubernetes-dashboard" --format="{{.ID}}"
.: exit status 1
E0626 21:08:30.849907   29069 logs.go:155] Failed to list containers for "storage-provisioner": running command: docker ps -a --filter="name=storage-provisioner" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22storage-provisioner%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=storage-provisioner" --format="{{.ID}}"
.: exit status 1
==> dmesg <==
[  +0,130196] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
[  +0,000004] acpi MSFT0101:00: platform device creation failed: -16
[  +0,840212] usb: port power management may be unreliable
[  +0,008586] platform eisa.0: EISA: Cannot allocate resource for mainboard
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 1
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 2
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 3
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 4
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 5
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 6
[  +0,000000] platform eisa.0: Cannot allocate resource for EISA slot 7
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 8
[  +0,034239] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,014524] Couldn't get size: 0x800000000000000e
[  +0,153324] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[  +0,035536] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000003] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,023124] i2c_hid i2c-ITE8350:00: i2c-ITE8350:00 supply vdd not found, using dummy regulator
[  +0,000023] i2c_hid i2c-ITE8350:00: i2c-ITE8350:00 supply vddl not found, using dummy regulator
[  +0,051130] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vdd not found, using dummy regulator
[  +0,000015] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vddl not found, using dummy regulator
[  +0,130110] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000001] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,203962] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000001] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,618460] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,202365] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +1,600817] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized!
[  +0,000003] uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not initialized!
[  +0,000001] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized!
[  +0,000002] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized!
[  +0,420493] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[  +2,809289] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[  +5,825351] PKCS#7 signature not signed with a trusted key
[  +0,000010] vboxdrv: loading out-of-tree module taints kernel.
[  +0,057157] PKCS#7 signature not signed with a trusted key
[  +0,000840] VBoxNetFlt: Successfully started.
[  +0,020507] PKCS#7 signature not signed with a trusted key
[  +0,001778] VBoxNetAdp: Successfully started.
[  +0,014385] PKCS#7 signature not signed with a trusted key
[  +0,000512] VBoxPciLinuxInit
[  +0,215649] kauditd_printk_skb: 36 callbacks suppressed
[jun26 20:26] test1
[  +0,000002] test2
[  +0,687483] VBoxPciLinuxLinuxUnload
[jun26 20:34] kauditd_printk_skb: 1 callbacks suppressed
[ +30,173124] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.

==> kernel <==
 21:08:30 up 44 min,  2 users,  load average: 0,78, 0,62, 0,57
Linux static-Aspire-R5-471T 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

==> kubelet <==
-- Logs begin at Sat 2018-04-28 17:18:10 -03, end at Wed 2019-06-26 21:08:30 -03. --
-- No entries --

The operating system version: Ubuntu 19.04

Comments: I found a workaround for that which is rm -fr .minikube/. But it is not intuitive at all.

[medyagh]

I think I have seen this error in the integration tests too !

[medyagh]

I think the least would could do is at least add solution message to the error map and have a link to this issue till we fix it
https://github.com/kubernetes/minikube/blob/master/pkg/minikube/problem/err_map.go

[staticdev]

@medyagh I think an even better approach is not trying to create a cluster when user tries minikube start --vm-driver=none without sudo (so this situation will stop occuring). You said on #4615 that there was a recent merged commit for this case.

[sharifelgamal]

Yeah, we now error out if you try creating a cluster with none driver without sudo. It'll be included in the next release.

[medyagh]

I confirm this issue I am making a PR to fix it. Thank you for reporting it and following up on it

[tstromberg]

@medyagh - any progress?

[tjj225]

having the same issue on macOS 10.14.3 (Mojave)

[dan-compton]

Bump -- just hit this myself

[progsri]

I worked for me after I deleted ~/.minikube directory ( looks like I had very old version of minikube v1.0.0 )..so the new version v1.3.1 could not use the old ~/.minikube directory.

[michalpiasecki1]

same issue for drivers: hyperv and virtualbox (on windows)

[tstromberg]

@michalpiasecki1 - Windows has a very different implementation model. My guess is your experience is likely related to Windows file locking. Please open a new issue.

[tstromberg]

This issue is fixed at head. We no longer require kubeadm to be in path.