The container is not yet running; the kubelet is still creating it (e.g. pulling the image, setting up volumes). This is often transient. If it persists, there may be an issue with image pull, volumes, or node resources.
Warning
N/A
- Report shows: Pod has container in state ContainerCreating
- kubectl describe pod shows state.waiting.reason: ContainerCreating
- Wait briefly; many pods move to Running after the image is pulled and the container starts
- If it stays in ContainerCreating, run kubectl describe pod and check Events
- Check node disk and inodes; ensure the node has capacity for the container rootfs and volumes
- For volume issues, verify PVCs are Bound and that secrets/configmaps exist
- Kubernetes docs: Pod lifecycle, Troubleshoot applications