Difference between revisions of "CrashLoopBackOff"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 8: | Line 8: | ||
== Related == | == Related == | ||
| − | * [[OOM]] | + | * <code>[[docker inspect]] grafana | grep -i [[OOM]]</code> |
* <code>[[kubectl describe pods]]</code> | * <code>[[kubectl describe pods]]</code> | ||
* <code>[[ebs-csi-controller]]</code> | * <code>[[ebs-csi-controller]]</code> | ||
Latest revision as of 21:25, 19 May 2026
CrashLoopBackOff
Init:CrashLoopBackOffkubectl get pods -A | grep CrashLoopBackOff
back-off 20s restarting failed container
Related[edit]
docker inspect grafana | grep -i OOMkubectl describe podsebs-csi-controllerkubectl get podspod_workers.go- K8s probes
- Kubernetes restartPolicy
- Minikube: storage-provisioner
See also[edit]
- Kubernetes init containers:
kubectl get pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff), initContainers:,Init:0/1 - CrashLoopBackOff
- 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,CrashLoopBackOff
Advertising:
