-
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
Unable to connect to the server error when try to kubectl run hello-minikube on minikube #1229
Comments
Can you post the output of |
Mar 08 11:15:02 minikube localkube[3804]: I0308 11:15:02.743250 3804 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/44899f60-03af-11e7-9e2f-00155d380105-default-token-gc489" (spec.Name: "default-token-gc489") pod "44899f60-03af-11e7-9e2f-00155d380105" (UID: "44899f60-03af-11e7-9e2f-00155d380105"). |
minikubeVM: Running |
Can you post the output of the following: |
Yes this is issue of virtual switch. I try many different ways and finally found that there was a little thing I was missing and that is just the restart the laptop after creating the switch. It works fine after that. Thanks |
Fun fact: "there was a little thing I was missing" won't help somebody with the same problem! ;) |
In my case it was proxy issue, when I do http_proxy=http://192.168.9.254:8080/ so I unset them as: unset http_proxy Now when I do I get my nodes listed without this error. Please check this solution if someone has proxy issue. |
Try this link |
Thanks, it was proxy problem! |
i had the same issue, |
BUG REPORT
Minikube version
v0.17.1
Environment:
What happened: When I try to run following command it gives me error
kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080
What you expected to happen: As documentation says,
deployment "hello-minikube" created
The text was updated successfully, but these errors were encountered: