Difference between revisions of "Init:ImagePullBackOff"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* <code>[[errImagePull]]</code> | * <code>[[errImagePull]]</code> | ||
* <code>[[pod_workers.go]]</code> | * <code>[[pod_workers.go]]</code> | ||
| + | * [[Registry]] | ||
== See also == | == See also == | ||
Latest revision as of 12:07, 7 December 2023
Init:ImagePullBackOff ImagePullBackOff
your-namespace elasticsearch-0 0/1 Init:ImagePullBackOff 0 2d5h your-namespace elasticsearch-1 0/1 Init:ImagePullBackOff 0 2d5h
- Solution: review output from
kubectl describe pod mypodname
Related[edit]
CrashLoopBackOffkubectl get nodes- PodInitializing
Warning BackOff 1s (x9 over 95s) kubelet Back-off restarting failed containerImagePullBackOfferrImagePullpod_workers.go- Registry
See also[edit]
- Kubernetes init containers:
kubectl get pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff), initContainers: kubectl get pods, kubectl describe pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff)- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising:
