Run a standard disk usage command on the host to find the offending storage path:
Note: CRFS works best with images compressed in the "stargz" format, which is an extension of the standard tar.gz format optimized for random access. cri file system tools link
+-------------------------------------------------------+ | Kubernetes Kubelet | +-------------------------------------------------------+ | v (CRI gRPC API) +-------------------------------------------------------+ | Container Runtime (containerd / CRI-O) | +-------------------------------------------------------+ | +--------------+--------------+ | | v v +-----------------------+ +-----------------------+ | Graph Drivers | | Storage Plugins | | (OverlayFS, btrfs) | | (CSI, Local Volumes) | +-----------------------+ +-----------------------+ | | v v +-----------------------+ +-----------------------+ | Episodic/Image Storage| | Persistent Storage | +-----------------------+ +-----------------------+ Run a standard disk usage command on the
- The source for configuration examples. Every Cri command that pulls an image, creates
Containers leak storage. Every Cri command that pulls an image, creates a layer, or writes logs consumes inodes. To diagnose "No space left on device" (ENOSPC) in Kubernetes, you must trace the link between the pod and its storage: