FailedMount ☸️ Kubernetes

Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition

The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.

Seen on: Kubernetes

Meaning

Events show FailedMount with the volume name and reason: the ConfigMap/Secret doesn’t exist, an NFS/CSI volume is unreachable, the PV is attached elsewhere, or the CSI driver isn’t running on the node.

Common causes

  • Referenced ConfigMap/Secret missing (or in another namespace)
  • PVC not bound or volume still attached to another node
  • NFS/EFS/CSI endpoint unreachable or driver pod down
  • Wrong permissions/fsGroup for the volume

⚡ Quick fix

  1. kubectl describe pod → read the FailedMount message
  2. Create the missing ConfigMap/Secret in the same namespace
  3. Check CSI driver pods and the PV/PVC status

Detailed fix by platform

Kubernetes

  1. bash
    kubectl get events -n app --field-selector reason=FailedMount
kubectl get pvc,pv -n app
kubectl get pods -n kube-system | grep -i csi

How to diagnose

  1. Volume — Which volume and why?
  2. Object — ConfigMap/Secret/PVC exists in this namespace?
  3. Driver — CSI pods healthy?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.