Cri File System Tools Install 〈CONFIRMED – 2024〉
sudo ls -la /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/23/fs Use du -sh to find the bloat:
With the installation steps and debugging workflows outlined above, you are now equipped to handle the most complex container storage issues on any CRI-compliant runtime. cri file system tools install
| Runtime | CRI Socket | Default CLI Tools | | :--- | :--- | :--- | | | /run/containerd/containerd.sock | ctr , nerdctl , crictl | | CRI-O | /run/crio/crio.sock | crictl , podman | | Docker (via cri-dockerd) | /run/cri-dockerd.sock | crictl (limited) | sudo ls -la /var/lib/containerd/io
sudo du -sh /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/*/fs | sort -h The largest directory is the culprit. With nerdctl , you can bypass low-level snapshot IDs: You must redirect it to your runtime
# OverlayFS tools are usually in the kernel; user-space helpers: sudo apt-get install -y fuse-overlayfs # For rootless sudo apt-get install -y attr # For xattr (getfattr/setfattr) sudo apt-get install -y util-linux # Provides findmnt , lsblk sudo apt-get install -y lsof # Shows open files within container mounts Configuring CRI Tools for Filesystem Access By default, crictl points to the Docker socket. You must redirect it to your runtime. Configure crictl Create /etc/crictl.yaml or ~/.config/crictl.yaml :