CRI-O
cri-o.io
- Free plan
- Linux
- API
- Self-hosted
7.0 Club score Visit cri-o.io
What the maker publishes
- Image registries
- CRI-O supports OCI container images and can pull images from any container registry. source
- Images
- CRI-O supports OCI container images and can pull images from any container registry. source
- Installation
- The project site provides RPM and DEB installation instructions and notes Fedora packaging is available. source
- Kubernetes compatibility
- CRI-O follows Kubernetes release cycles and its n-2 version-skew policy for feature graduation, deprecation, or removal. source
- License
- The project repository identifies its license as Apache-2.0. source
- Linux platform
- The installation guide assumes a Linux machine and describes packages for Debian-based and Red Hat-based distributions. source
- Monitoring
- The conmon utility monitors containers, handles logging, serves attach clients, and detects out-of-memory situations. source
- Networking
- CRI-O uses CNI for pod networking, and its site names Flannel, Weave, and OpenShift-SDN as tested plugins. source
- Project boundary
- Building, signing, and pushing images to image storage are outside the stated scope of the CRI-O project. source
- Project status
- CRI-O identifies itself as a community-driven open source project and a graduated Cloud Native Computing Foundation project. source
- Purpose
- CRI-O implements the Kubernetes Container Runtime Interface so Kubernetes can launch and manage OCI containers. source
- 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. source
- Runtime support
- CRI-O supports OCI-compatible runtimes, including runc and Kata Containers. source
- Security
- The project describes container security separation using SELinux, capabilities, seccomp, and other policies specified by OCI. source
- Storage
- Its storage library supports OverlayFS, devicemapper, AUFS, and btrfs, with OverlayFS as the default driver. source
- Support
- The project site directs users to the #crio channel on Kubernetes Slack and the project GitHub repository. source
- Support and community
- The project directs users to GitHub issues and pull requests for discussions and to the Kubernetes Slack channel for chat. source
- Vulnerability information
- CRI-O publishes signed OpenVEX reports with releases to indicate which dependency vulnerabilities are reachable in CRI-O code paths. source
- Vulnerability reporting
- Security reports are handled by community volunteers, and the project says reporters can expect an initial response within three business days. source
Checked against the maker's pages on 7 Oct 2026.