# Package manager sudo apt remove cri-tools # Debian/Ubuntu sudo dnf remove cri-tools # RHEL/Fedora
To summon these tools, Alex had to ensure the environment was prepared. Because the tools were built on the .NET Framework 4.0
Displays CPU, memory, and disk usage for running container file systems. crictl rmi --prune Safely removes unused storage layers from the host machine. cri file system tools install
View the filesystem layers and structural metadata of an image. sudo crictl inspecti Use code with caution. 3. Check Container Disk Usage
Which ( containerd or CRI-O ) is your cluster currently running? What Linux distribution are your worker nodes using? # Package manager sudo apt remove cri-tools #
These tools are usually third-party utilities used to unpack files (CRI Packed Files).
For more control over the version, you can manually download and install: View the filesystem layers and structural metadata of
# Move binaries to system path sudo cp nydus-static/* /usr/local/bin/
Mastering CRI File System Tools: A Comprehensive Installation Guide
Kubernetes relies on the Container Runtime Interface (CRI) to manage container lifecycles, images, and file systems. When debugging node-level issues, standard Docker commands will not work if your cluster uses containerd or CRI-O. You need the official CRI tools—specifically crictl and critest —to inspect the container file system, check image layers, and validate runtime performance.