Difference between revisions of "ContainerCreating"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
* <code>[[FailedMount]]</code> | * <code>[[FailedMount]]</code> | ||
* <code>[[kubectl get pods -A]]</code> | * <code>[[kubectl get pods -A]]</code> | ||
− | * [[ | + | * [[kubectl get events]] |
+ | * [[Why is my Amazon EKS pod stuck in the ContainerCreating state with the error "failed to create pod sandbox"?]] | ||
== See also == | == See also == |
Revision as of 14:11, 22 February 2024
Failed to load logs: container "shell" in pod "node-shell-c3426092-d677-4b35-b848-b8df42de0f2e" is waiting to start: ContainerCreating Reason: BadRequest (400)
Failed to load logs: container "sentry-web" in pod "sentry-web-79b8bbccdf-5t6nz" is waiting to start: ContainerCreating Reason: BadRequest (400)
Related
Running
kubectl get pods
FailedMount
kubectl get pods -A
- kubectl get events
- Why is my Amazon EKS pod stuck in the ContainerCreating state with the error "failed to create pod sandbox"?
See also
kubectl get pods, -l, -n
,Running, Pending, Init
, ContainerCreating, ImagePullBackOff,Init:ImagePullBackOff, Terminating, ErrImagePull, Completed, InvalidImageName,kube-system
,ls_containers.sh
kubectl get pods, kubectl describe pods, Init: (Init:ErrImagePull, Init:CrashLoopBackOff, Init:ImagePullBackOff)
- Pods:
kubectl apply
,kubectl [ pod get | top | delete | describe pods ]
,InitContainers, PodInitializing, CrashLoopBackOff, ImagePullPolicy:, NodeAffinity, NodeSelector, Terminated
Advertising: