hyperkit + docker proxy: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection #4589
Comments
|
does this issue happen on re-starting miniukube or on first start ? |
|
have you verified that you can access docker hub through proxy ? |
medyagh
added
the
triage/needs-information
|
|
@medyagh in minikube ssh, |
|
@dfang Could you show the final solution here ? I met same problem... |
|
for me hyperkit driver on mac had same issue. switching to vmwarefusion made the trick, though not a solution if you want to use hyperkit |
|
Hi,
stderr:
|
|
Had the same issue on windows+virtualbox+minihube. Problem was the DNS. By adding |
After stopping minikube VM, I added nameserver server 8.8.8.8 to /etc/resolv.conf in minikube VM (deployed on HyperV) and then started the VM but the issue still persists. |
|
I have the same issue. tried what vikas86 did (on mac+minikube+virtualbox).. to no avail. |
|
Finally narrowed down the issue, for which the solution is providing public network access to minikube VM. For minikube to pull images it needs to have a public network access which can be done by creating a Virtual network switch in HyperV or something equivalent in virtualbox (NAT or Bridge). In HyperV create a virtual network switch (type external) - all default settings.
This solves below issues while starting minikube:
|
|
I am using KVM with minikube on linux and facing the same issue, not able to fetch any of the public images from docker hub |
|
Worked.. https_proxy= minikube --profile profile_name start --docker-env http_proxy= --docker-env https_proxy= --docker-env no_proxy=192.168.99.0/24 Details here : https://kubernetes.io/docs/setup/learning-environment/minikube/#starting-a-cluster |
@spsarolkar make sure you are able to access public network from your minikube VM. |
|
Hi! Im still problem with pull images via MiniKube ` $ docker pull nginx:alpine my minikube starts on Windows 10 via cmd : info during starts minikube : `
Regards |
|
If anyone faces the same problem on MacOS, this fixes it (you will need to install VirtualBox first): IMHO this issue should not be closed, as there should be a way to run |
|
@massenz : please open a new issue, if you continue to have issues with Using --vm-driver virtualbox is of course a workaround, but like you say the native one should work |
|
Good point, done: see #6296 |
Would like to add I was unable to run the command for creating the switch, those who are facing the issue try this , I am using hyperkit VM and running on MACOS Mojave. But even after running this problem still persists, I was just trying to spin off nginx container inside a pod using this pod.yml minikube start --vm-driver=hyperkit --hyperv-virtual-switch="My virtual switch" |
|
I'm running into same issue on MacOS mojave. Damn near about to drop kick my laptop. Neither of the fixes are working for me. |
|
@wpdildine - see #6296 TL;DR: |
|
I somehow ran into exactly the same problem, even after multiple
|
This worked for my on my mac! |
This did the trick for me on my Linux Box- worked straight away with VirtualBox. Tried running minikube on docker before that and almost went crazy! |
It worked fine for me on mac. Thanks! |
|
But why go through all that, if a much simpler (IMHO) is to just install Virtualbox and do this: |
|
Those of you commenting on other drivers, you might want to add your thoughts to #8135 The VirtualBox driver and the so called "native virtualization" drivers (HyperKit/HyperV/libvirt) will remain, even if the Docker/Podman drivers are available. The question is which should be default. There is a new option called See also https://minikube.sigs.k8s.io/docs/drivers/ The intro kubernetes course still uses VirtualBox... |
|
Fair enough, @afbjorklund, I wasn't "commenting" on other drivers: I was just noting the weird and wonderful contortions folks were going through (also, worth noting, very temporary and manual), and thought I'd suggest a simpler way. For that matter, there's also #6296, which I dutifully filed following your suggestions; unfortunately that one seems to have stalled for now. |
This works for me. By default the vm driver would be 'hyperkit' unless otherwise specified. |
It doesn't work for me. However...
...works fine. |
emm... virtualbox is too heavy, minikube at least start 3 VMs, dell 7050 with 8GB ram and intel i7-6700, system frozen. |
Didn't work for me on Mac 😞 |
|
Same issue here under hyperkit |
|
I did a restart after doing the following upon restart |
|
on windows 10, Docker -> Setup -> Resources -> enable Manual DNS config value=8.8.8.8 remenber is windows |
|
I still have this issue, why is this closed without an explanation? |
|
Agreed - this issue has not been resolved to a point that explains how to correct this issue. Adding the DNS resolution entries as stated above has not changed the behavior or minikube being able to pull or to resolve hosts. |
|
@sspieker-cc: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hi, guys. Though I am not familiar with the codes, yet ,I figured out an workaround for this problem. |
does this help your case #4589 (comment) ? |
|
@arashbi @wpdildine |
|
It happens on hyperkit, I am not sure what you mean by docker driver |
|
yes, i still have the issue with docker driver on the latest version |
tstromberg
changed the title
tstromberg
changed the title
tstromberg
changed the title
tstromberg
changed the title
tstromberg
added
the
cause/firewall-or-proxy
|
Based on the messages, I'm pretty confident that this is a proxy configuration issue, and a very old one at that. Marking as obsolete, as the handling has changed since 2019. If you run into a similar problem, please open a new issue. |
and others
Switched to docker for mac long ago, since minikube new version support load balancer, i tried it today.
but i can't pull any images.
The exact command to reproduce the issue:
The full output of the command that failed:
after startup, change to minikube context
minikube addons list | grep dnsshows nothings ? is that the problem, why kube-dns, coredns removed ?docker infoshows HTTP_PROXY, HTTPS_PROXY are correctly configured.where is the configuration for docker in minikube ssh ?
The output of the
minikube logscommand:The operating system version:
macOS 10.14.5
The text was updated successfully, but these errors were encountered: