Kubernetes New Added 8 September 2026

Kubernetes: Unable to attach or mount volumes, timed out

The pod is stuck in ContainerCreating because a volume never attached. With cloud block storage the usual reason is that the disk is still attached to another node, or the volume lives in a zone where the pod cannot be scheduled, since a ReadWriteOnce volume can only be mounted on one node at a time.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

kubectl describe pod POD | grep -A10 Events
kubectl get volumeattachment | grep PV_NAME

# Zone mismatch: the pod must land where the disk is
kubectl get pv PV -o jsonpath='{.spec.nodeAffinity}'
kubectl get nodes -L topology.kubernetes.io/zone

# Old pod still holding it (common after a node goes NotReady)
kubectl delete pod OLD_POD --grace-period=0 --force

# Use WaitForFirstConsumer so the volume is created in the pod's zone
volumeBindingMode: WaitForFirstConsumer

How to diagnose Kubernetes errors

Kubernetes errors are best read as a state machine that got stuck. Pending means the scheduler could not place the pod (resources, taints, or an unbound volume). ImagePullBackOff means kubelet could not fetch the image (name, credentials, or registry). CrashLoopBackOff means the container starts and exits, so the answer is in the container's own logs. OOMKilled means the kernel killed it for exceeding its memory limit. Each state points at a different subsystem, and kubectl describe almost always contains the exact reason in its events.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Start with kubectl describe pod <name> and read the Events section at the bottom. It names the precise failure, including registry errors and scheduling constraints.
For CrashLoopBackOff, read the previous container's logs: kubectl logs <pod> --previous. The current container may not have produced output yet.
Check resource pressure with kubectl top pod and kubectl top node, and compare against the pod's requests and limits.
Test RBAC directly: kubectl auth can-i <verb> <resource> --as=system:serviceaccount:<ns>:<sa>. This answers permission questions definitively.
For networking, confirm the Service has endpoints (kubectl get endpoints) before suspecting DNS, Ingress or the CNI.

Tools worth reaching for

kubectl describe
kubectl logs --previous
kubectl auth can-i
kubectl top
kubectl events --sort-by=.lastTimestamp
k9s

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

kubernetes.io

Related Kubernetes errors

See all 34 Kubernetes errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.