-
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
hyperkit: tcp: lookup k8s.gcr.io read: connection refused #4594
Comments
Possibly related: images also could not be fetched when I tried using
All the failure messages from the Also possibly related:
|
Here are some diagnostic commands: DNS
Hyperkit install
Docker registries
|
I am curious, are you trying to pull image to minikube? have you done minikube docker-env ? |
I wonder if this is related to this #4547 |
I was able to get things working using |
@medyagh for me, I start minikube without --insecure-registry, with or without HTTP_PROXY, HTTPS_PROXY, docker pull in minikube ssh
can't pull alpine images on docker hub, needless to say images on gcr.io. how dns work in minikube ? can't find any documentation. by the way. on macOS version 10.14.5, minikube version 1.2.0, hyperkit driver didn't try other driver yet .... |
I don't have |
See #3036 (comment) on issue #3036. Cisco Umbrella and Cisco Anyconnect may run a local DNS proxy which does not seem to work with Hyperkit and minikube. I am not using any sort of HTTP proxy. A temporary workaround for me is to use the parallels vm-driver. I do not experience this issue with Parallels. I did not test Virtualbox or VMware. |
I found out that I had dnsmasq running on my Mac. Aber disabling it, I downloaded the newest hyperkit driver, deleted the exisiting minikube and set up a new minikube. Now everything works as expected.
Hopefully this helps someone. |
@chaimleib - any chance there is a local DNS server running on your system? You can confirm using:
If so, this is due to #3036 |
@chaimleib could you confirm the output of |
Copying from above:
|
Thanks for the info! It does appear that you have a DNS server (dnscrypt) which conflicts with the hyperkit DNS server. You can either use VirtualBox or kill the dnscrypt process before hand. Closing as dupe of #3036 |
I'm having trouble fetching docker images using hyperkit. This affects the initial minikube start command logged below, where it says "Unable to pull images..."
The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version:
macOS 10.14.5
The text was updated successfully, but these errors were encountered: