minikube: DNS not working inside minikube pods since 23.6
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report
Please provide the following details:
Environment:
Minikube version (use minikube version): v0.24.1
- OS (e.g. from /etc/os-release): Mac OS 10.12.6
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): v0.23.6.iso - Install tools: Homebrew
- Others: Kubernetes version 1.7.5, containers built using Alpine 3.6
What happened:
I first noticed this issues when I wasn’t able to reach Dockerhub inside a pod, but it looks like DNS is failing globally. I can ping 8.8.8.8, but if I try to reach anything using DNS, it fails.
/networking # nslookup registry-1.docker.io
nslookup: can't resolve '(null)': Name does not resolve
/networking # nslookup google.com
nslookup: can't resolve '(null)': Name does not resolve
/ # cat /etc/resolv.conf
nameserver 10.0.0.10
search default.svc.cluster.local svc.cluster.local cluster.local
options ndots:5
Pinging 10.0.0.10 also fails to connect.
This used to work when I was on version .21. It’s broken since I upgraded to .23.6 and .24.1.
What you expected to happen:
DNS to work.
How to reproduce it (as minimally and precisely as possible):
Start a pod using this yaml with the API version added:
kind: Pod
metadata:
generateName: networking-
labels:
test: test
spec:
containers:
- image: ceridwen/networking:v1
imagePullPolicy: Always
name: networking
readinessProbe:
tcpSocket:
port: 5000
initialDelaySeconds: 5
periodSeconds: 1
restartPolicy: Always
I also saw this using the docker:stable-dind image.
Output of minikube logs (if applicable):
I didn’t see anything in the logs that looked relevant, I can post them if needed.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 20
- Comments: 29 (5 by maintainers)
I’m still seeing the same problem with: Mac OS: Darwin 10.15.7 Minikube: v1.18.1 Kubernetes: v1.20.2 Docker 20.10.3 VirtualBox: 6.1.18 r142142
Same issue:
Linux MInt 18.3 Minikube: 0.25.0 Kubernetes: v1.9.2
I’m haveing the same issue in Windows 10.
Minikube: 0.25.0 Kubernetes: v1.9.0
💯 it has to do with pulling the latest version of the minikube iso (0.23.6). Downgrading to 0.23.5 we no longer have this issue.
2 of us at our company are able to reproduce on Mac OSX 10.12.6 using k8s v1.8.0.
~Doesn’t matter which bootstrapper we use (
kubeadmorlocalkube) or which VM driver.~ We’ve tried every possible combo of both.You can specify the actual Minikube ISO version like so:
As an aside, any reason the ISO semantic version is different than the minikube semantic version? That through us for a loop as well… 😄
I was facing the same problem and solved with this:
I was getting
CrashLoopBackOffforkube-dns-7bb84f958d-6sglbpod and these logs:I hope this helps.
DNS broken for me as well after upgrading to minikube 0.24.1 (probably broke in a preceding version) on macOS 10.12.6.
Solved by recreating the cluster by
minikube delete(warning: this will remove all of your data) followed by aminikube start.I can reproduce the issue with k8s v1.7.5 on Linux… It doesn’t seem to be a Mac-only issue.
I have the same issue:
minikube version: v0.29.0 kubernetes version: 1.10.0 kubectl version: 1.12.0 Ubuntu 18.04.1 LTS VM Driver: none kube-dns addon: enabled
I have a CrashLoopBackOff of coredns with this log:
I completely tear down and recreate for my use case and still have an issue.