Open kevinkirkup opened 7 years ago
Looks like this was being caused by having dnsmasq
enabled. Not sure why that would be though.
After disabling dnsmasq
everything seems to be working correctly.
@kevinkirkup Thanks for advice. I’ll check this isuue later.
I just hit the same issue and have been wasting hours trying to figure out why I could not build an image inside minikube when following the tutorial - I kept getting errors "read: connection refused" when trying to pull an image off of dockerhub. This post guided me to turning off dnsmasq, which I forgot I even had on this laptop, CHEERS!
@kevinkirkup @jasonmacdonald thanks a lot, disabling dnsmasq helped me too. Dnsmasq was installed as dependency to valet to service .dev domain. Is there any way to make them work simultaneously?
@kevinkirkup if you're using local dnsmasq, you need to tell the dnsmasq listen docker host interface as well.
~ cat /usr/local/etc/dnsmasq.conf |grep -i listen-add
#listen-address=
listen-address=127.0.0.1
listen-address=192.168.64.1
don't forget to reload dnsmasq service, after editing configuration file.
I'm working in a corporate network and I need to have the VM hosting the docker daemon to include the DNS servers for our network, otherwise I can't download the OpenShift/Kubernetes images to start a cluster in
minikube
/minishift
.This doesn't seem to be and issue when I use
docker-machine
.I've been able to get around this by adding the DNS servers to
resolve.conf
andresolved.conf
after the VM has been created. Due to changes inminishift
however, this no longer works.Is there a way to specify addition DNS servers that can be configured? Is there a configuration that I should be checking?
Version Info