Closed hatharom closed 4 years ago
Hello, thank you for sharing.
ping xyz.com
-> works well , got responsecurl xyz.com
-> just hangs
ICMP(ping) is no problem, but HTTP connection has a problem. It looks like networking or proxy problem.
Is your machine through VPN network or proxy? And could you check the PROXY env is set correctly?
See about vpn and proxy: https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/
Also helpful would be the full output of the minikube start --alsologtostderr -v=1
command.
I am not behind a proxy. Outside of minikube I can reach everything without any proxy settings. When I launch docker for windows I still can pull anything - step into the container and can reach everything on the net - without any proxy configuration. And minikube 1.9.0. has been working well also.
Here are the logs for minikube start:
edit: Forgot to mention one difference to the 1.9.0. 1.9.0 was started by minikube start , but before 1.9.2 start I have set the default driver to hyper-v. (Since then I am unable to unset it because it says I cant set it to 'none')
@hatharom - my guess is that the Virtual Switch that minikube is using does not have internet access. Can you include the output of minikube start --alsologtostderr -v=1
?
I think the solution here might involve reconfiguring or adding a new Virtual Switch and specifying --hyperv-external-switch
, but in the mean-time, you sounds like you can use minikube start --driver=docker
as well.
Thanks your response. External switch for hyper-v didnt solved it. So I changed the driver back to docker.
Steps to reproduce the issue: Minikube was working fine until I upgraded to 1.9.2 1.
minikube delete
thenminikube start
works fine (started with hyper-v driver) 2.minikube status show:3.Launching
helm init
. Tiller says ImagePullBackOff because of timeout. First I thought it is a helm issue. But the I ssh-d into minikube 4.minikube ssh
ping xyz.com
-> works well , got responsecurl xyz.com
-> just hangsdocker pull anything*
-> timeout*by anything I mean really..anything: tiller:
docker pull helm's tiller gcr.io/kubernetes-helm/tiller:v2.16.5
some common image:docker pull postgres
; image already on minikube: docker pulldocker k8s.gcr.io/etcd
Full output of failed command: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Optional: Full output of
minikube logs
command: