Minikube: Getting issue when I do minikube start. How do I solve it?

[redoz94]

Steps to reproduce the issue:

1.% minikube start
😄 minikube v1.11.0 on Darwin 10.15.4
✨ Using the hyperkit driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing hyperkit VM for "minikube" ...
🐳 Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
❌ Problems detected in kubelet:
Jul 15 11:06:41 minikube kubelet[2508]: E0715 11:06:41.557283 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:06:45 minikube kubelet[2508]: E0715 11:06:45.674199 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 10s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:06:45 minikube kubelet[2508]: E0715 11:06:45.704470 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:06:48 minikube kubelet[2508]: E0715 11:06:48.930083 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 10s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:06:56 minikube kubelet[2508]: E0715 11:06:56.312598 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
❌ Problems detected in kubelet:
Jul 15 11:07:07 minikube kubelet[2508]: E0715 11:07:07.322396 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:07:19 minikube kubelet[2508]: E0715 11:07:19.319395 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:07:22 minikube kubelet[2508]: E0715 11:07:22.823415 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:07:28 minikube kubelet[2508]: E0715 11:07:28.948635 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:07:33 minikube kubelet[2508]: E0715 11:07:33.115203 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
❌ Problems detected in kubelet:
Jul 15 11:07:33 minikube kubelet[2508]: E0715 11:07:33.115203 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:07:35 minikube kubelet[2508]: E0715 11:07:35.701058 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:07:50 minikube kubelet[2508]: E0715 11:07:50.317024 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:03 minikube kubelet[2508]: E0715 11:08:03.320306 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:04 minikube kubelet[2508]: E0715 11:08:04.084644 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:07:50 minikube kubelet[2508]: E0715 11:07:50.317024 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:03 minikube kubelet[2508]: E0715 11:08:03.320306 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:04 minikube kubelet[2508]: E0715 11:08:04.084644 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:08 minikube kubelet[2508]: E0715 11:08:08.939887 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:08:03 minikube kubelet[2508]: E0715 11:08:03.320306 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:04 minikube kubelet[2508]: E0715 11:08:04.084644 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:08 minikube kubelet[2508]: E0715 11:08:08.939887 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:17 minikube kubelet[2508]: E0715 11:08:17.318931 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:22 minikube kubelet[2508]: E0715 11:08:22.314573 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:08:08 minikube kubelet[2508]: E0715 11:08:08.939887 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:17 minikube kubelet[2508]: E0715 11:08:17.318931 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:22 minikube kubelet[2508]: E0715 11:08:22.314573 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:30 minikube kubelet[2508]: E0715 11:08:30.318678 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:37 minikube kubelet[2508]: E0715 11:08:37.322662 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:08:17 minikube kubelet[2508]: E0715 11:08:17.318931 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:22 minikube kubelet[2508]: E0715 11:08:22.314573 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:30 minikube kubelet[2508]: E0715 11:08:30.318678 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:37 minikube kubelet[2508]: E0715 11:08:37.322662 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 40s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:08:42 minikube kubelet[2508]: E0715 11:08:42.316320 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 1m20s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
❌ Problems detected in kubelet:
Jul 15 11:08:54 minikube kubelet[2508]: E0715 11:08:54.649707 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:08:55 minikube kubelet[2508]: E0715 11:08:55.694269 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:08 minikube kubelet[2508]: E0715 11:09:08.317405 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:10 minikube kubelet[2508]: E0715 11:09:10.047614 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:18 minikube kubelet[2508]: E0715 11:09:18.934353 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:09:08 minikube kubelet[2508]: E0715 11:09:08.317405 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:10 minikube kubelet[2508]: E0715 11:09:10.047614 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:18 minikube kubelet[2508]: E0715 11:09:18.934353 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:23 minikube kubelet[2508]: E0715 11:09:23.323755 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:29 minikube kubelet[2508]: E0715 11:09:29.310235 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
❌ Problems detected in kubelet:
Jul 15 11:09:10 minikube kubelet[2508]: E0715 11:09:10.047614 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:18 minikube kubelet[2508]: E0715 11:09:18.934353 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:23 minikube kubelet[2508]: E0715 11:09:23.323755 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:29 minikube kubelet[2508]: E0715 11:09:29.310235 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:38 minikube kubelet[2508]: E0715 11:09:38.321093 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
❌ Problems detected in kubelet:
Jul 15 11:09:29 minikube kubelet[2508]: E0715 11:09:29.310235 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:38 minikube kubelet[2508]: E0715 11:09:38.321093 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:43 minikube kubelet[2508]: E0715 11:09:43.317233 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
Jul 15 11:09:52 minikube kubelet[2508]: E0715 11:09:52.330668 2508 pod_workers.go:191] Error syncing pod 3d83851205ef38fb7489910db37ce6db ("etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"), skipping: failed to "StartContainer" for "etcd" with CrashLoopBackOff: "back-off 2m40s restarting failed container=etcd pod=etcd-minikube_kube-system(3d83851205ef38fb7489910db37ce6db)"
Jul 15 11:09:54 minikube kubelet[2508]: E0715 11:09:54.330027 2508 pod_workers.go:191] Error syncing pod 25f3f4d4ded8e0a243ee69038f73a4d3 ("kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"), skipping: failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff: "back-off 1m20s restarting failed container=kube-apiserver pod=kube-apiserver-minikube_kube-system(25f3f4d4ded8e0a243ee69038f73a4d3)"
🤦 Unable to restart cluster, will reset it: apiserver health: apiserver healthz never reported healthy: cluster wait timed out during healthz check
💥 initialization failed, will try again: run: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.18.3:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.18.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Unfortunately, an error has occurred:
    timed out waiting for the condition

This error is likely caused by:
    - The kubelet is not running
    - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
    - 'systemctl status kubelet'
    - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.

Here is one example how you may list all Kubernetes containers running in docker:
    - 'docker ps -a | grep kube | grep -v pause'
    Once you have found the failing container, you can inspect its logs with:
    - 'docker logs CONTAINERID'

stderr:
W0715 11:10:07.596053 8278 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
W0715 11:10:09.393182 8278 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
W0715 11:10:09.394271 8278 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

💣 Error starting cluster: run: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.18.3:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.18.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Unfortunately, an error has occurred:
    timed out waiting for the condition

This error is likely caused by:
    - The kubelet is not running
    - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
    - 'systemctl status kubelet'
    - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.

Here is one example how you may list all Kubernetes containers running in docker:
    - 'docker ps -a | grep kube | grep -v pause'
    Once you have found the failing container, you can inspect its logs with:
    - 'docker logs CONTAINERID'

stderr:
W0715 11:12:05.261552 21952 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
W0715 11:12:06.850564 21952 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
W0715 11:12:06.851666 21952 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose

💣 failed to start node: startup failed: run: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.18.3:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap": Process exited with status 1
stdout:
[init] Using Kubernetes version: v1.18.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Unfortunately, an error has occurred:
    timed out waiting for the condition

This error is likely caused by:
    - The kubelet is not running
    - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
    - 'systemctl status kubelet'
    - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.

Here is one example how you may list all Kubernetes containers running in docker:
    - 'docker ps -a | grep kube | grep -v pause'
    Once you have found the failing container, you can inspect its logs with:
    - 'docker logs CONTAINERID'

stderr:
W0715 11:12:05.261552 21952 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
W0715 11:12:06.850564 21952 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
W0715 11:12:06.851666 21952 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose

1. 
   3.

Full output of failed command:

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

[priyawadhwa]

Hey @redoz94 thanks for opening this issue.

Could you let me know if either of these works?

minikube delete
minikube start --driver hyperkit

minikube delete
minikube start --driver hyperkit --force-systemd

[sharifelgamal]

Did either of the above suggestions works @redoz94?

[medyagh]

Hi @redoz94, I haven't heard back from you, I wonder if you still have this issue?
Regrettably, there isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but please feel free to reopen whenever you feel ready to provide more information.

[newtoniumx3]

Thank you @priyawadhwa I had this issue on windows 10 after a reboot and simply running
minikube delete then minikube start

The delete was the key that fixed my connection issues

[newtoniumx3]

Hey quick follow up. Actually every single time I reboot my machine the error keeps coming back!
The fix everytime is to re-run minikube delete minikube start

Why is this happening? (windows 10 pro)
! Unable to restart cluster, will reset it: apiserver health: apiserver healthz never reported healthy: cluster wait timed out during healthz check

[vyom-soft]

Same here, I am also facing the same issue.

[misha-fm]

@newtoniumx3 I also had this issue, that after I restart my computer, minikube start fails unless you delete the cluster and recreate it again. What I figured out, that in order to avoid this problem, one should stop the cluster before shutting down the computer: minikube stop. Then after reboot minikube start executes successfully and the cluster is up and running. Hope this helps you.

[mconner]

@misha-fm, I get a similar problem. I've found that if I restart my computer, then do minikube start and it fails, if I then do a minikube stop , followed by a minikube start, that usually fixes it. I assume a proper shutdown is clearing the problem.

[vdovinanton]

Ditto