Skip to content
Back to the playbook

Diagnosing containerd task-creation timeouts

containerdKuberneteskubectlrevision 1

Diagnostic tree

  1. In progresscontainerd task creation is timing outThis deadline is a CRI-level timeout, not an application error — something is slowing down containerd's own container-creation path on the affected node(s).
View the whole map (7 more steps)
  • Is this happening on one node or across the cluster?
  • Root cause: likely a cluster-wide containerd/CRI or network issue
  • Check the affected node's resource pressure and containerd's own health
  • Root cause: the node is resource-starved, usually on disk
  • Is there a large pile-up of stale containers or images on this node?
  • Fix: remove the stale exited containers
  • Node and containerd both look healthy

What to test

containerd task creation is timing out

This deadline is a CRI-level timeout, not an application error — something is slowing down containerd's own container-creation path on the affected node(s).

What happened?