coreDNS CrashLoopBackoff

I have set up the cluster without error and am running through Lab 2.1. I noticed that the pods for coreDNS are failing.
I am running the nodes on bare metal.
Debug info is:
**kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE calico-etcd-wr2cf 1/1 Running 3 13h calico-kube-controllers-57c8947c94-g2lbc 1/1 Running 3 13h calico-node-lsjm9 2/2 Running 17 13h calico-node-zhgnd 2/2 Running 9 13h coredns-576cbf47c7-56thg 0/1 CrashLoopBackOff 54 13h coredns-576cbf47c7-nmznf 0/1 CrashLoopBackOff 54 13h etcd-nuc1 1/1 Running 4 13h kube-apiserver-nuc1 1/1 Running 4 13h kube-controller-manager-nuc1 1/1 Running 3 13h kube-proxy-ct89j 1/1 Running 3 13h kube-proxy-lbdxr 1/1 Running 5 13h kube-scheduler-nuc1 1/1 Running 3 13h
kubectl describe pods -n kube-system coredns-576cbf47c7-56thg
Name: coredns-576cbf47c7-56thg Namespace: kube-system Priority: 0 PriorityClassName: <none> Node: nuc1/10.10.0.53 Start Time: Sat, 29 Dec 2018 23:06:32 +1100 Labels: k8s-app=kube-dns pod-template-hash=576cbf47c7 Annotations: <none> Status: Running IP: 192.168.21.71 Controlled By: ReplicaSet/coredns-576cbf47c7 Containers: coredns: Container ID: docker://5491ac6a53be7f653036af7baaecfb318679882d3ad4b60c7c02b8846f3a4f9d Image: k8s.gcr.io/coredns:1.2.2 Image ID: docker-pullable://k8s.gcr.io/coredns@sha256:3e2be1cec87aca0b74b7668bbe8c02964a95a402e45ceb51b2252629d608d03a Ports: 53/UDP, 53/TCP, 9153/TCP Host Ports: 0/UDP, 0/TCP, 0/TCP Args: -conf /etc/coredns/Corefile State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Sun, 30 Dec 2018 12:39:49 +1100 Finished: Sun, 30 Dec 2018 12:39:50 +1100 Ready: False Restart Count: 54 Limits: memory: 170Mi Requests: cpu: 100m memory: 70Mi Liveness: http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5 Environment: <none> Mounts: /etc/coredns from config-volume (ro) /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-zwdp6 (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: config-volume: Type: ConfigMap (a volume populated by a ConfigMap) Name: coredns Optional: false coredns-token-zwdp6: Type: Secret (a volume populated by a Secret) SecretName: coredns-token-zwdp6 Optional: false QoS Class: Burstable Node-Selectors: <none> Tolerations: CriticalAddonsOnly node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 13h default-scheduler Successfully assigned kube-system/coredns-576cbf47c7-56thg to nuc1 Warning NetworkNotReady 13h (x8 over 13h) kubelet, nuc1 network is not ready: [runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized] Normal Pulled 13h (x4 over 13h) kubelet, nuc1 Container image "k8s.gcr.io/coredns:1.2.2" already present on machine Normal Created 13h (x4 over 13h) kubelet, nuc1 Created container Normal Started 13h (x4 over 13h) kubelet, nuc1 Started container Warning BackOff 12h (x255 over 13h) kubelet, nuc1 Back-off restarting failed container Normal SandboxChanged 3h31m (x2 over 3h31m) kubelet, nuc1 Pod sandbox changed, it will be killed and re-created. Warning BackOff 3h31m (x3 over 3h31m) kubelet, nuc1 Back-off restarting failed container Normal Pulled 3h30m (x2 over 3h31m) kubelet, nuc1 Container image "k8s.gcr.io/coredns:1.2.2" already present on machine Normal Created 3h30m (x2 over 3h31m) kubelet, nuc1 Created container Normal Started 3h30m (x2 over 3h31m) kubelet, nuc1 Started container Normal Pulled 3h29m (x4 over 3h30m) kubelet, nuc1 Container image "k8s.gcr.io/coredns:1.2.2" already present on machine Normal Created 3h29m (x4 over 3h30m) kubelet, nuc1 Created container Normal Started 3h29m (x4 over 3h30m) kubelet, nuc1 Started container Warning BackOff 3h5m (x124 over 3h30m) kubelet, nuc1 Back-off restarting failed container Warning FailedMount 92m kubelet, nuc1 MountVolume.SetUp failed for volume "coredns-token-zwdp6" : couldn't propagate object cache: timed out waiting for the condition Normal SandboxChanged 91m (x2 over 92m) kubelet, nuc1 Pod sandbox changed, it will be killed and re-created. Normal Pulled 90m (x4 over 91m) kubelet, nuc1 Container image "k8s.gcr.io/coredns:1.2.2" already present on machine Normal Created 90m (x4 over 91m) kubelet, nuc1 Created container Normal Started 90m (x4 over 91m) kubelet, nuc1 Started container Warning BackOff 57m (x169 over 91m) kubelet, nuc1 Back-off restarting failed container Normal SandboxChanged 49m (x2 over 50m) kubelet, nuc1 Pod sandbox changed, it will be killed and re-created. Normal Pulled 47m (x4 over 49m) kubelet, nuc1 Container image "k8s.gcr.io/coredns:1.2.2" already present on machine Normal Created 47m (x4 over 49m) kubelet, nuc1 Created container Normal Started 47m (x4 over 49m) kubelet, nuc1 Started container Warning BackOff 4m49s (x214 over 49m) kubelet, nuc1 Back-off restarting failed container
Comments
-
@bryonbaker ,
You can try to delete the 2 coredns pods, and they will be re-created.
Are you in Lab 2.1 of LFD259?
Thanks,
-Chris0 -
Hi,
The issue is actually thoroughly documented in the CoreDNS web site. It is caused because CoreDNS is detecting a loopback and it terminates. It is expected behaviour.The solution is to change the DNS setting in /etc/resolv.conf. For those using Ubuntu I have documented what to do here as it can be tricky - especially with Ubuntu Desktop edition.
There are other ways to solve it but in the end I set up an external DNS server with bind9 for resolving hostnames. Overkill I know.1
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 555 Linux Foundation Boot Camps
- 297 Cloud Engineer Boot Camp
- 119 Advanced Cloud Engineer Boot Camp
- 52 DevOps Engineer Boot Camp
- 54 Cloud Native Developer Boot Camp
- 4 Express Training Courses
- 4 Express Courses - Discussion Forum
- 1.9K Training Courses
- 18 LFC110 Class Forum
- 7 LFC131 Class Forum
- 25 LFD102 Class Forum
- 150 LFD103 Class Forum
- 17 LFD121 Class Forum
- LFD137 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 598 LFD259 Class Forum
- 102 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 3 LFS203 Class Forum
- 69 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 34 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 92 LFS260 Class Forum
- 130 LFS261 Class Forum
- 32 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS281 Class Forum
- 221 LFW211 Class Forum
- 168 LFW212 Class Forum
- SKF100 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 761 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 141 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 478 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 66 Mobile Computing
- 23 Android
- 29 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 536 Off Topic
- 131 Introductions
- 216 Small Talk
- 21 Study Material
- 817 Programming and Development
- 275 Kernel Development
- 508 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 59 All In Program
- 59 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)