Error restarting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition

[Thomas-In]

Hello,

I got the following error, can you help?

root@minikube:~# minikube start --container-runtime=cri-o
o minikube v1.0.1 on linux (amd64)
$ Downloading Kubernetes v1.14.1 images in the background ...
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
: Re-using the currently running virtualbox VM for "minikube" ...
: Waiting for SSH access ...

• "minikube" IP address is 192.168.99.100
• Configuring CRI-O as the container runtime ...
• Version of container runtime is 1.13.1
  : Waiting for image downloads to complete ...
• Preparing Kubernetes environment ...
• Pulling images required by Kubernetes v1.14.1 ...
  : Relaunching Kubernetes v1.14.1 using kubeadm ...
  : Waiting for pods: apiserver
  ! Error restarting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition

[tstromberg]

@Thomas-In - You should upgrade to a more recent release of minikube.

In the mean-time, you can likely fix the issue by running minikube delete, but you will probably run into the issue again until you upgrade. Also, please don't run minikube as root.

Let me know how it goes.

[Thomas-In]

Thanks to Thomas Strömberg for help. As you advise, it works. Excellent!!!

…

On Sun, Apr 19, 2020 at 2:22 PM Thomas Strömberg ***@***.***> wrote: @Thomas-In <https://github.com/Thomas-In> - You should upgrade to a more recent release of minikube. In the mean-time, you can likely fix the issue by running minikube delete, but you will probably run into the issue again until you upgrade. Also, please don't run minikube as root. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APEWHCZGU2XZKPV5HDGDVHLRNKDCDANCNFSM4MLRTZIQ> .

[medyagh]

glad to see this was solved