restart: waiting for k8s-app=kube-proxy: timed out waiting for the condition

[serverok]

When i minikube start, i get error

boby@sok-01:~$ minikube start
😄  minikube v0.35.0 on linux (amd64)
💡  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🔄  Restarting existing virtualbox VM for "minikube" ...
⌛  Waiting for SSH access ...
📶  "minikube" IP address is 192.168.99.100
🐳  Configuring Docker as the container runtime ...
✨  Preparing Kubernetes environment ...
🚜  Pulling images required by Kubernetes v1.13.4 ...
🔄  Relaunching Kubernetes v1.13.4 using kubeadm ... 
⌛  Waiting for pods: apiserver proxy💣  Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new
boby@sok-01:~$ 

I am using Ubuntu 18.04

Attached minikube logs

minikube-logs.txt

[staticdev]

I have the same issue here... only difference is I am running on Ubuntu 18.10.

nonrootuser $ minikube start
😄  minikube v0.35.0 on linux (amd64)
💡  Tip: Use 'minikube start -p <name>' 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 Docker as the container runtime ...
✨  Preparing Kubernetes environment ...
🚜  Pulling images required by Kubernetes v1.13.4 ...
🔄  Relaunching Kubernetes v1.13.4 using kubeadm ... 
⌛  Waiting for pods: apiserver proxy💣  Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

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

minikube-logs.txt

[lee-zhg]

I encountered the same problem after moved to v0.35.0 to fix the other problem.

😄 minikube v0.35.0 on darwin (amd64)
👍 minikube will upgrade the local cluster from Kubernetes 1.13.3 to 1.13.4
💡 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 Docker as the container runtime ...
✨ Preparing Kubernetes environment ...
💾 Downloading kubeadm v1.13.4
💾 Downloading kubelet v1.13.4
🚜 Pulling images required by Kubernetes v1.13.4 ...
🔄 Relaunching Kubernetes v1.13.4 using kubeadm ...
⌛ Waiting for pods: apiserver

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

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

I am on v10.14.2

[mverrilli]

I did minikube delete and started it again and it worked. It did sit on Waiting for pods for a few minutes but did get past it (unlike before, I left it running for a long time without any progress). HTH. I am also running 0.35.0.

[chandrabhandz]

Having the same problem, just installed 0.35.0 and can't get it to work.
tried minikube delete and start again but no luck

😄 minikube v0.35.0 on darwin (amd64)
🔥 Creating virtualbox VM (CPUs=4, Memory=8192MB, Disk=20000MB) ...
📶 "minikube" IP address is 192.168.99.102
🐳 Configuring Docker as the container runtime ...
✨ Preparing Kubernetes environment ...
🚜 Pulling images required by Kubernetes v1.13.4 ...
🚀 Launching Kubernetes v1.13.4 using kubeadm ...
⌛ Waiting for pods: apiserver proxy💣 Error starting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

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

[tstromberg]

@serverok - I've seen this to when resuming a previously setup VM, but haven't been able to replicate it reliably. Do you mind attaching the output of the following command:

minikube ssh 'docker logs $(docker ps -a -f name=k8s_kube-proxy --format={{.ID}})'

I suspect this can be resolved by running minikube delete, but it's almost certainly going to come back at some random point in the future.

For other folks who are also running into this in a way that does not say "Error restarting", I suggest opening a new bug report as there are likely to be multiple causes. Feel free to reference #3843 though.

Thanks!

Update: Fixed command-line.

[ocontant]

I have the same issue when running minikube with Virtualbox and the starting commands:

I run the minikube command as my user (not root).
minikube start --memory=8192 --cpus=4 --kubernetes-version=v1.13.4 --extra-config=controller-manager.cluster-signing-cert-file="/var/lib/localkube/certs/ca.crt" --extra-config=controller-manager.cluster-signing-key-file="/var/lib/localkube/certs/ca.key"

I run Ubuntu 18.10 inside a VMWare Workstation virtualization engine.
I have CPU Intel VT-x/EPT and IOMMU enabled on the VM and in the BIOS of the baremetal host.

The host has 32G of RAM and I allocated 16G RAM and 4 vCPU to the Ubuntu VM. I setup the minikube to start with 8G RAM and 4 CPU.

[tstromberg]

@ocontant - If you don't mind, please open a new issue as it may have different root causes. Many of those command-line options seem very strange, as localkube is no longer used.

I had a bug in my example command: please use:

minikube ssh 'docker logs $(docker ps -a -f name=k8s_kube-proxy --format={{.ID}})'

Thanks!

[ocontant]

@ocontant - If you don't mind, please open a new issue as it may have different root causes. Many of those command-line options seem very strange, as localkube is no longer used.

I had a bug in my example command: please use:

minikube ssh 'docker logs $(docker ps -a -f name=k8s_kube-proxy --format={{.ID}})'

Thanks!

The command are from the istio page reference how to install istio in minikube. Pershaps their documention is a bit outdate. I will try without those parameters and see.

[ocontant]

@tstromberg Seems like removing the extra parameters fixed the issue. My instance of minikube started correctly.

Do you have a way to inform istio upstream that their documentation is deprecated and they should update it? Reference to the documentation: [(https://istio.io/docs/setup/kubernetes/platform-setup/minikube/)]

[serverok]

@tstromberg

There is no such container, here is the result

boby@sok-01:~$ minikube start
😄  minikube v0.35.0 on linux (amd64)
💡  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🔄  Restarting existing virtualbox VM for "minikube" ...
⌛  Waiting for SSH access ...
📶  "minikube" IP address is 192.168.99.100
🐳  Configuring Docker as the container runtime ...
✨  Preparing Kubernetes environment ...
🚜  Pulling images required by Kubernetes v1.13.4 ...
🔄  Relaunching Kubernetes v1.13.4 using kubeadm ... 
⌛  Waiting for pods: apiserver proxy💣  Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new
boby@sok-01:~$ minikube ssh 'docker logs $(docker ps -a -f name=k8s_kube-proxy --format={{.ID}})'
"docker logs" requires exactly 1 argument.
See 'docker logs --help'.

Usage:  docker logs [OPTIONS] CONTAINER

Fetch the logs of a container
ssh: Process exited with status 1
boby@sok-01:~$ 

Attached result of docker ps and docker ps -a inside "minikube ssh"

docker-ps.txt