Skip to content
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

coredns in error / CrashLoopBackOff #4096

Closed
goyalnikhil02 opened this issue Apr 14, 2019 · 4 comments
Closed

coredns in error / CrashLoopBackOff #4096

goyalnikhil02 opened this issue Apr 14, 2019 · 4 comments
Labels
co/coredns CoreDNS related issues priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@goyalnikhil02
Copy link

kube-system coredns-86c58d9df4-qk56b 0/1 Error 451 15d
kube-system coredns-86c58d9df4-zwnjq 0/1 CrashLoopBackOff 463 15d

How to fix this issue.
minikube dashboard is also not working.
It this the reason for above ?
Error:
503 Service Unavailable from Dashboard UI

@tstromberg
Copy link
Contributor

Hey @goyalnikhil02 - Do you mind providing:

  • The full minikube start command you are using
  • What operating system you are on
  • The output of kubectl describe pod <name of coredns pod> -n kube-system

In this case, would be either coredns-86c58d9df4-qk56b or coredns-86c58d9df4-zwnjq

Thanks!

@tstromberg tstromberg changed the title kube-dns error coredns in error / CrashLoopBackOff Apr 22, 2019
@tstromberg tstromberg added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it. co/coredns CoreDNS related issues labels Apr 22, 2019
@champly
Copy link

champly commented May 10, 2019

i meet the same trouble, i use this to resolve
#3511

@tstromberg
Copy link
Contributor

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

@conanswp
Copy link

I meet the same trouble. After update docker from docker-ensgine to docker-ce and use command minikube --driver=none start --extra-config=kubelet.resolv-conf=/etc/resolv.conf solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/coredns CoreDNS related issues priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants