Back-off restarting failed container (BackOff)
Revision as of 06:24, 18 July 2024 by Welcome (talk | contribs) (Welcome moved page BackOff to Back-off restarting failed container over redirect)
kubectl get events -A your_namespace 30m Warning BackOff 1s (x9 over 95s) kubelet Back-off restarting failed container
kubectl describe pod your-pod Warning BackOff 3m20s (x34 over 8m21s) kubelet Back-off restarting failed container
3m7s Warning BackOff pod/ubuntu Back-off restarting failed container ubuntu in pod ubuntu_default(798217e6-2f92-41bf-8f77-e88490b07ba2)
kubectl get events your_namespace 30m Warning BackoffLimitExceeded job/your-job27740460 Job has reached the specified backoff limit
Related
ImagePullBackOffBack-off restarting failed containerJob has reached the specified backoff limit- ProbeWarning
- Reason
See also
- BackOff: Back-off restarting failed container
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ],kubectl events, kubectl get events:BackOff,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity,FailedScheduling, kubectl describe events, Unhealthy,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded - 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:
