-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shadowsock proxy: kube-proxy configmap update: timed out: Unable to register node connection refused #3031
Comments
I consistently get the reported behavior. I also see the following in the
I can also add that if I try again repeatedly it eventually works. Environment: Minikube version (use
|
Also getting this behavior when attempting to start minikube with the kvm2 driver. |
I am having same problem...I tried on ubuntu 16.04, LUbuntu 16.04 and 18. Tired of setting up minikube on Ubuntu. Could anyone guide on how to resolve this ? minikube version: v0.28.2 output - |
I am seeing this problem as well on MacOS High Sierra and the VMware Fusion Driver. |
Running to the same issue here using same config as @efengx with the exception that I am using vmwarefusion |
Same issue here with the same configuration as @JTG2020 |
same here Ubuntu 18 |
I am also having this issue. Lots of log entries like
|
Hello this is my first post so don't mind missing precision,
in a regular non admin cmd shell Just let me know if it works for you as well and if you think the privileges are too risky (on a private W-lan) |
FWIW, this sounds like either a firewall or routing issue, where the host is not configured to be able to contact the VM it installs. |
The issue is happening on laptop. Is there anything that needs to be checked?
Because I can start and stop VM with sudo.
…Sent from my iPad
On Sep 18, 2018, at 7:04 PM, Thomas Strömberg ***@***.***> wrote:
FWIW, this sounds like either a firewall or routing issue, where the host is not configured to be able to contact the VM it installs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
My environment has similar issue. I upgrade minikube to 0.30. It failed with below message for command " minikube start -p cluster1 --kubernetes-version v1.11.0" "E1028 21:47:30.342880 23752 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" |
We are having the same issue
update: |
MacOs Mojave 10.14 I got the same exact issue and |
Somehow I could resolve the issue by running ubuntu in unsecured mode and minikube started successfully. My issue #3031 (comment) is resolved now but i don't think this is correct resolution. |
I managed to resolve the issue by starting
|
This worked for me as well! :) |
this actually helped me as well, but not just that, it didn't work as i expected, here's what i did: now restart your computer (this did the trick for me, i did all these steps without restarting with no luck) $ brew cask reinstall minikube but when you want to start minikube provide kubernetes version to it now use it like so: Note: you have to prefix 'v' to the version otherwise it won't work. all these steps has been posted by others, i just ran them in this order and it worked. |
Related: #3145 |
This worked perfectly for me. Thanks |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube, and if the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience! |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Please provide the following details:
Environment:
macOS High Sierra(MacBook Pro (Retina, 15-inch, Mid 2015))
Docker version 18.06.0-ce, build 0ffa825
kubectl version:v1.10.2
Minikube version (use
minikube version
): v0.28.2cat: /etc/os-release: No such file or directory
cat ~/.minikube/machines/minikube/config.json | grep DriverName
): "DriverName": "virtualbox",cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):"Boot2DockerURL": "file:///Users/ofengx/.minikube/cache/iso/minikube-v0.28.1.iso"The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
What happened:
What you expected to happen: Can start correctly
How to reproduce it (as minimally and precisely as possible): minikube start
Output of
minikube logs
(if applicable):Anything else do we need to know:
Using the Chinese network
Shadowsock + ss + global Mode
The text was updated successfully, but these errors were encountered: