CRI-O
cri-o.io
Spec sheet
- Purpose
- CRI-O implements the Kubernetes Container Runtime Interface so Kubernetes can launch and manage OCI containers.Read 7 Oct 2026 · cri-o.io
- Security
- The project describes container security separation using SELinux, capabilities, seccomp, and other policies specified by OCI.Read 7 Oct 2026 · cri-o.io
- Support
- The project site directs users to the #crio channel on Kubernetes Slack and the project GitHub repository.Read 7 Oct 2026 · cri-o.io
- License
- The project repository identifies its license as Apache-2.0.Read 7 Oct 2026 · github.com
- Image registries
- CRI-O supports OCI container images and can pull images from any container registry.Read 7 Oct 2026 · cri-o.io
- Images
- CRI-O supports OCI container images and can pull images from any container registry.Read 7 Oct 2026 · cri-o.io
- Installation
- The project site provides RPM and DEB installation instructions and notes Fedora packaging is available.Read 7 Oct 2026 · cri-o.io
- Kubernetes compatibility
- CRI-O follows Kubernetes release cycles and its n-2 version-skew policy for feature graduation, deprecation, or removal.Read 7 Oct 2026 · github.com
- Linux platform
- The installation guide assumes a Linux machine and describes packages for Debian-based and Red Hat-based distributions.Read 7 Oct 2026 · github.com
- Monitoring
- The conmon utility monitors containers, handles logging, serves attach clients, and detects out-of-memory situations.Read 7 Oct 2026 · cri-o.io
- Networking
- CRI-O uses CNI for pod networking, and its site names Flannel, Weave, and OpenShift-SDN as tested plugins.Read 7 Oct 2026 · cri-o.io
- Project boundary
- Building, signing, and pushing images to image storage are outside the stated scope of the CRI-O project.Read 7 Oct 2026 · github.com
- Project status
- CRI-O identifies itself as a community-driven open source project and a graduated Cloud Native Computing Foundation project.Read 7 Oct 2026 · cri-o.io
- Release artifacts
- The v1.37.2 release page lists static bundles and describes SHA-256 checksums, cosign signatures, SPDX bills of materials, OpenVEX reports, and SLSA provenance artifacts.Read 7 Oct 2026 · github.com
- Runtime support
- CRI-O supports OCI-compatible runtimes, including runc and Kata Containers.Read 7 Oct 2026 · cri-o.io
- Storage
- Its storage library supports OverlayFS, devicemapper, AUFS, and btrfs, with OverlayFS as the default driver.Read 7 Oct 2026 · cri-o.io
- Support and community
- The project directs users to GitHub issues and pull requests for discussions and to the Kubernetes Slack channel for chat.Read 7 Oct 2026 · github.com
- Vulnerability information
- CRI-O publishes signed OpenVEX reports with releases to indicate which dependency vulnerabilities are reachable in CRI-O code paths.Read 7 Oct 2026 · github.com
- Vulnerability reporting
- Security reports are handled by community volunteers, and the project says reporters can expect an initial response within three business days.Read 7 Oct 2026 · github.com
Where Specifiction places it
- Container Engines#21 of 317.3
- Container Runtime Software#21 of 287.4
