Difference between revisions of "Init:CrashLoopBackOff"
Jump to navigation
Jump to search
(13 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[kubectl get pods]] | [[kubectl get pods]] | ||
+ | |||
+ | elasticsearch-0 0/1 [[Init:]][[CrashLoopBackOff]] 6 6m45s | ||
+ | elasticsearch-1 0/1 [[Init:]]CrashLoopBackOff 6 6m45s | ||
== Related == | == Related == | ||
* [[OOM]] | * [[OOM]] | ||
+ | * <code>[[kubectl exec -it]]</code> | ||
+ | * [[CrashLoopBackOff]] | ||
== See also == | == See also == | ||
− | * {{ | + | * {{Kubectl init containers}} |
+ | * {{K8s troubleshooting}} | ||
+ | * {{Pods}} | ||
+ | |||
+ | [[Category:K8s]] |
Latest revision as of 10:38, 21 September 2023
kubectl get pods
elasticsearch-0 0/1 Init:CrashLoopBackOff 6 6m45s elasticsearch-1 0/1 Init:CrashLoopBackOff 6 6m45s
Related[edit]
See also[edit]
- Kubernetes init containers:
kubectl get pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff), initContainers:
- 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
- Pods:
kubectl apply
,kubectl [ pod get | top | delete | describe pods ]
,InitContainers, PodInitializing, CrashLoopBackOff, ImagePullPolicy:, NodeAffinity, NodeSelector, Terminated
Advertising: