calico node - Init:ImagePullBackOff

kkarthik

Not able to pull image from docker.io repository.

ubuntu@k8s:~$ kubectl -n kube-system get pods
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-78d6f96c7b-s8b79 0/1 Pending 0 10h
calico-node-f9wr4 0/1 Init:ImagePullBackOff 0 93m
coredns-59b45cd7d6-d7tbn 0/1 Pending 0 10h
coredns-59b45cd7d6-lbzql 0/1 Pending 0 10h
etcd-k8s 1/1 Running 0 10h
kube-apiserver-k8s 1/1 Running 0 10h
kube-controller-manager-k8s 1/1 Running 0 10h
kube-proxy-wvhm9 1/1 Running 0 10h
kube-scheduler-k8s

Name: k8s
Roles: control-plane,master
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=k8s
kubernetes.io/os=linux
node-role.kubernetes.io/control-plane=
node-role.kubernetes.io/master=
Annotations: kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp: Mon, 05 Jul 2021 12:33:54 -0400
Taints: node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoSchedule
Unschedulable: false
Lease:
HolderIdentity: k8s
AcquireTime:
RenewTime: Mon, 05 Jul 2021 22:48:07 -0400
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
MemoryPressure False Mon, 05 Jul 2021 22:44:18 -0400 Mon, 05 Jul 2021 12:33:53 -0400 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Mon, 05 Jul 2021 22:44:18 -0400 Mon, 05 Jul 2021 12:33:53 -0400 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Mon, 05 Jul 2021 22:44:18 -0400 Mon, 05 Jul 2021 12:33:53 -0400 KubeletHasSufficientPID kubelet has sufficient PID available
Ready False Mon, 05 Jul 2021 22:44:18 -0400 Mon, 05 Jul 2021 12:33:53 -0400 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Addresses:
InternalIP: 10.173.225.195
Hostname: k8s
Capacity:
cpu: 4
ephemeral-storage: 15396784Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 6103748Ki
pods: 110
Allocatable:
cpu: 4
ephemeral-storage: 14189676111
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 6001348Ki
pods: 110
System Info:
Machine ID: e6ac9cc16f364ed5914e629033969e1a
System UUID: 2C3C0242-92E5-E153-A978-C529520CA2CB
Boot ID: dbbcfe73-8cd4-49ed-a010-565c4564de10
Kernel Version: 4.15.0-142-generic
OS Image: Ubuntu 16.04.7 LTS
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://18.9.7
Kubelet Version: v1.21.2
Kube-Proxy Version: v1.21.2
PodCIDR: 192.168.0.0/24
PodCIDRs: 192.168.0.0/24
Non-terminated Pods: (6 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age
--------- ---- ------------ ---------- --------------- ------------- ---
kube-system calico-node-f9wr4 250m (6%) 0 (0%) 0 (0%) 0 (0%) 95m
kube-system etcd-k8s 100m (2%) 0 (0%) 100Mi (1%) 0 (0%) 10h
kube-system kube-apiserver-k8s 250m (6%) 0 (0%) 0 (0%) 0 (0%) 10h
kube-system kube-controller-manager-k8s 200m (5%) 0 (0%) 0 (0%) 0 (0%) 10h
kube-system kube-proxy-wvhm9 0 (0%) 0 (0%) 0 (0%) 0 (0%) 10h
kube-system kube-scheduler-k8s 100m (2%) 0 (0%) 0 (0%) 0 (0%) 10h
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 900m (22%) 0 (0%)
memory 100Mi (1%) 0 (0%)
ephemeral-storage 100Mi (0%) 0 (0%)
hugepages-1Gi 0 (0%) 0 (0%)
hugepages-2Mi 0 (0%) 0 (0%)
Events:
ubuntu@k8s:~$

chrispokorni

Hi @kkarthik,

It seems you deviated slightly from the installation guide, where we begin by installing Kubernetes v1.20.1 (and upgrade to v1.21.1 in a future lab exercise). The calico pods are fully deployed once you reach Lab exercise 3.3 and remove the taint from the control plane node.

Is the custom pod network 192.168.0.0/24 reflected in both calico.yaml and kubeadm-config.yaml files?

Regards,
-Chris