Minikube: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

[freew01f]

I am a new in using minikube
I installed minikube in Macos 10.14 depended brew
and I installed virtuabox and docker
when I run minikube start, I waited for a very long time.
I got these

Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E1119 13:20:32.476720   24107 start.go:302] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
    minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]: E1119 13:20:56.497303   24107 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: read tcp 192.168.3.5:63686->172.217.31.234:443: read: connection reset by peer

how can I fix them?
my version of minikube is minikube version: v0.29.0
thanks

[zaoying]

have you try below?
minikube delete
minikube start

[freew01f]

have you try below?
minikube delete
minikube start

I tried them many times， but the same result

[zaoying]

try this:

minikube logs | grep image

if you see "failed pulling image" in the log, then you should use proxy,
I am not success yet!
Yes! I succeed run minikube by adding proxy:

On Windows environment, you must use administrative power shell or command line to execute below script!

Step One

start minikube VM

minikube start

Step Two

open a new terminal and ssh into the minikube VM

minikube ssh

Step Three

acquire the IP address of minikube VM, the "eth0" Network Adapter is what we need

ifconfig

Step Four

stop the running minikube VM by press Ctrl+C in the original terminal, then run

minikube stop

Step Five

assume the above IP is 192.168.99.xxx, port is up to your proxy client configure

minikube start --docker-env HTTP_PROXY=http://192.168.99.1:8118 --docker-env HTTPS_PROXY=http://192.168.99.1:8118 --docker-env NO_PROXY=127.0.0.1/24

According some other issues, the latest version minikube don't work well with the above script

Here I offer my ultimate solution !

Just run Step One to Step Three's scripts, then create dir docker.system.d and file https-proxy.conf

sudo mkdir /etc/systemd/system/docker.service.d
sudo vi /etc/systemd/system/docker.service.d/https-proxy.conf

type this content into file https-proxy.conf

[Service]
Environment="HTTPS_PROXY=https://proxy.example.com:443/"

then flush changes and restart Docker

sudo systemctl daemon-reload
sudo systemctl restart docker

finally exit the ssh session and re-create the minikube VM

exit
minikube delete
minikube start

[jeffwubj]

with latest codes from master, I cannot start cluster successfully as well with proxy parameters, I finally replaced all image urls with reachable ones then can start minikube successfully.

[tstromberg]

There's a bad sign that this machine has connectivity issues, such as a misconfigured proxy:

Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: read tcp 192.168.3.5:63686->172.217.31.234:443: read: connection reset by peer

3145 has the longer term feature fix for detecting these issues.

[stevegy]

i had the same error message in my recent trying. When i removed my HTTP_PROXY and NO_PROXY to test and the kubectl get nodes return my node info, that remind me the NO_RPOXY setting. Finally, i found my issue was caused by my Windows NO_PROXY setting was not properly covered my HyperV VM ip address. So the kubectl connect to the proxy first for my VM ip.

[Walther]

Commenting here too: I got a similar error state by having ran minikube start after VirtualBox installation _without rebooting my mac_. After having rebooted after the virtualbox installation && running minikube delete & minikube start, I got into a working state. More details in the other issue linked above

[freew01f]

Commenting here too: I got a similar error state by having ran minikube start after VirtualBox installation _without rebooting my mac_. After having rebooted after the virtualbox installation && running minikube delete & minikube start, I got into a working state. More details in the other issue linked above

let me try

[freew01f]

I fixed the problem, I am in China, so I can not connect some website inside the virtual box,
I install the http proxy and run minikube this way

minikube start --docker-env HTTP_PROXY=http://192.168.99.1:8118 --docker-env HTTPS_PROXY=http://192.168.99.1:8118 --docker-env NO_PROXY=127.0.0.1/24 --registry-mirror=https://registry.docker-cn.com

[matrixkar]

Run
Linux Mint
1.- sudo usermod -aG docker $USER
2.- sudo /etc/init.d/docker restart
3.- su ${USER}
4.- sudo minikube delete
5.- sudo minikube start

[rosberglinhares]

have you try below?
minikube delete
minikube start

I was getting this error because first I run minikube start, got an error and then run minikube start --vm-driver=none. Thanks!

[luis-allan]

Commenting here too: I got a similar error state by having ran minikube start after VirtualBox installation _without rebooting my mac_. After having rebooted after the virtualbox installation && running minikube delete & minikube start, I got into a working state. More details in the other issue linked above

this works for me.