DNS failure trying to build docker image in hello-minikube tutorial #1442
Comments
aaron-prindle
added
the
kind/support
|
In order to pull images you have to make sure that the DNS pod is running in your cluster. To do this you can run |
|
Thanks @aaron-prindle. > kubectl get po --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system kube-addon-manager-minikube 0/1 ContainerCreating 0 1m
> kubectl describe pod kube-addon-manager-minikube --namespace kube-system
Name: kube-addon-manager-minikube
Namespace: kube-system
Node: minikube/192.168.64.7
Start Time: Sat, 06 May 2017 17:46:07 +0100
Labels: component=kube-addon-manager
kubernetes.io/minikube-addons=addon-manager
version=v6.4-alpha.1
Annotations: kubernetes.io/config.hash=4fb35b6f38517771d5bfb1cffb784d97
kubernetes.io/config.mirror=4fb35b6f38517771d5bfb1cffb784d97
kubernetes.io/config.seen=2017-05-06T16:46:02.325082498Z
kubernetes.io/config.source=file
Status: Pending
IP: 192.168.64.7
Controllers: <none>
Containers:
kube-addon-manager:
Container ID:
Image: gcr.io/google-containers/kube-addon-manager:v6.4-alpha.1
Image ID:
Port:
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Requests:
cpu: 5m
memory: 50Mi
Environment: <none>
Mounts:
/etc/kubernetes/ from addons (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
addons:
Type: HostPath (bare host directory volume)
Path: /etc/kubernetes/
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: =:Exists:NoExecute
Events: <none>
> kubectl logs kube-addon-manager-minikube --namespace kube-system
Error from server (BadRequest): container "kube-addon-manager" in pod "kube-addon-manager-minikube" is waiting to start: ContainerCreating |
|
I've managed to complete the hello-minikube tutorial using VirtualBox, rather than xhyve. Not sure if that helps? |
|
I have the same issue as @jabley following the tutorial https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/ Here's the output of the status Pod Status: Pod detail I don't have a firewall running on this machine, and I can access the service from my mac |
|
I'm not familiar with minikube (starting off with kubernetes) so I'm not sure if there's meant to be a DNS service at I feel like editing the Edit: 😂 That change isn't persisted once I exit the ssh process.. |
|
I also encountered this DNS failure following the Hello Minikube tutorial using the xhyve driver. Like @jabley, when I switched to the virtualbox driver properly, I could build the Docker image. My MacOS X version is 10.12.5, minikube version is v0.19.1, and other versions are the same. The minikube DNS pod doesn't seem to be running with the xhyve driver. With the VirtualBox driver: |
|
This should be the xhyve driver issue. minikube delete -> minikube start (don't use --vm-driver=xhyve, by default minikube will start by using VirtualBox driver), then everything is fine. |
|
I have kube-dns problems, but they are slightly different. I do get the pods to start with xhyve: But cluster-info doesn't show kube-dns info and I can't get I also tried to use VirtualBox but for that as well If I try to Same happens for just |
|
I think maybe is the expected result when we run "kubectl cluster-info" on minikube? mine is the same. If I run the command on Google Container Engine, that's the real kubernetes cluster implementation. All displayed. |
|
Thanks @kamusis , when you do It's also possible I don't understand how and where and if the resolving should work with minikube. Edit. Also this doesn't work: which I got from kubernetes/kubernetes#16836 (comment) and does seem to work there. |
|
@ttiurani |
|
Having the same issue as @ttiurani . Can't get local image registry working with xhyve (haven't tried with VirtualBox) due to the DNS issue... Has anyone solved this? |
|
Just found out why pulling the image failed. The default |
|
If someone is still facing this issue on
The full details are mentioned here |
|
I had the exact same issue with the xhyve driver where the docker build would fail and where the nslookup within the minikube ssh session would fail as well. Starting minikube with the virtualbox driver works succesfully. I also had dnsmasq running locally to configure anything .dev to resolve to localhost. After disabling and removing dnsmasq locally and starting minikube with xhyve again everything works succesfully. Maybe this info helps? |
|
Same exact issue as @daxhuiberts .In my case, dns failed when hyperkit driver and dnsmasq running. Work normally when disabled dnsmasq and restart minikube. |
|
Faced the same issue with both hyperkit and xhyve drivers. Looks like dnsmasq was refusing connections on the Host IP address(in this case 192.168.64.1) assigned by minikube. Configuring dnsmasq to specifically listen on the minikube host IP address did the trick for me. Add the following 2 lines in your dnsmasq.conf. You will need to restart your macbook after updating dnsmasq config. |
|
I saw the same error too when I ran The steps mentioned by @kamusis here in #1442 (comment) worked for me. Switching to virtualbox fixed this issue for me. I stopped minikube, deleted it, started it without I do see the This issue does look like an |
|
Uninstalling |
The .dev TLD is owned by Google and has been added to the HTTP Strict Transport Protocol preload list. See https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/ I don't use the .dev thing anyway, or any dnsmasq configuration. I suspect dnsmasq is causing kubernetes/minikube#1442 so I'm removing it.
|
uninstalling dnsmasq works for me |
|
I had the exact same issues with the hyperkit driver, under macOS 10.13. I already had dnsmasq installed via homebrew from a project I did a couple of years ago. @gautamkpai's solution worked for me. Between having dnsmasq installed, and the little snitch firewall, I wonder if anyone else encounters issues, or if it just happens to be this convergence of existing software on the host system. Edit: After considering whether of not I actually needed dnsmasq, I opted to remove it. That worked fine, so both solutions seem to work. |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
removed
the
lifecycle/stale
k8s-ci-robot
added
the
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Moved from kubernetes/website#3596
Minikube version (use
minikube version):> minikube version minikube version: v0.18.0Environment:
cat ~/.minikube/machines/minikube/config.json | grep DriverName): "DriverName": "xhyve",cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): "Boot2DockerURL": "file:///Users/jabley/.minikube/cache/iso/minikube-v0.18.0.iso",What happened:
Trying to follow the hello-minikube tutorial:
What you expected to happen:
The
docker buildto succeed.How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
The text was updated successfully, but these errors were encountered: