cri-o /cri-o
Open Container Initiative-based implementation of Kubernetes Container Runtime Interface
★ 5,693⑂ 1,226👁 121⑃ 8,761● 1,724▤ 312
+1
日增长
5,693
stars
1,226
forks
121
watchers
8,761
prs
1,724
issues
312
releases
README
!CRI-O logo
CRI-O - OCI-based implementation of Kubernetes Container Runtime Interface
- Compatibility matrix: CRI-O ⬄ Kubernetes
- What is the scope of this project?
- What is not in the scope of this project?
- Roadmap
- CI images and jobs
- Commands
- Configuration
- Security
- OCI Hooks Support
- CRI-O Usage Transfer
- Communication
- Awesome CRI-O
- Getting started
- Installing CRI-O
- Running Kubernetes with CRI-O
- The HTTP status API
- Metrics
- Tracing
- Container Runtime Interface special cases
- Debugging tips
- Adopters
- Weekly Meeting
- Governance
- AI Assistants
- License Scan
Compatibility matrix: CRI-O ⬄ Kubernetes
CRI-O follows the Kubernetes release cycles with respect to its minor versions
(1.x.y). Patch releases (1.x.z) for Kubernetes are not in sync with those from
CRI-O, because they are scheduled for each month, whereas CRI-O provides
them only if necessary. If a Kubernetes release goes End of
Life,
then the corresponding CRI-O version can be considered in the same way.
This means that CRI-O also follows the Kubernetes n-2 release version skew
policy when it comes to feature graduation, deprecation or removal. This also
applies to features which are independent from Kubernetes. Nevertheless, feature
backports to supported release branches, which are independent from Kubernetes
or other tools like cri-tools, are still possible. This allows CRI-O to decouple
from the Kubernetes release cycle and have enough flexibility when it comes to
implement new features. Every feature to be backported will be a case by case
decision of the community while the overall compatibility matrix should not be
compromised.
For more information visit the Kubernetes Version Skew
Policy.
| CRI-O | Kubernetes | Maintenance status |
| ------------------------------- | ------------------------------- | --------------------------------------------------------------------- |
| main branch | master branch | Features from the main Kubernetes repository are actively implemented |
| release-1.x branch (v1.x.y) | release-1.x branch (v1.x.z) | Maintenance is manual, only bugfixes will be backported. |
The release notes for CRI-O are hand-crafted and can be continuously retrieved
from our GitHub pages website.
What is the scope of this project?
CRI-O is meant to provide an integration path between OCI conformant runtimes and
the Kubelet.
Specifically, it implements the Kubelet Container Runtime Interface (CRI)
using OCI conformant runtimes.
The scope of CRI-O is tied to the scope of the CRI.
At a high level, we expect the scope of CRI-O to be restricted to the following functionalities:
- Support multiple image formats including the existing Docker image format
- Support for multiple means to download images including trust & image verification
- Container Top issues
#7586Reloading CRI-O configuration using SIGHUP overrides settings passed through command-line arguments36 comments · 2023-12-12#4941crio authentification with mirrored registry 25 comments · 2021-05-25#9242Proposal: Add `never_wipe_images` Configuration Option to Prevent Image Storage Wiping22 comments · 2025-06-02#9865hostUsers: false with fuse-overlayfs driver mounts unwritable rootfs in container19 comments · 2026-04-01#8541Add option to enable only UNIX socket for metrics endpoint15 comments · 2024-09-02#10188Integration suite hangs after every test has passed, job cancelled at the 2h timeout14 comments · 2026-07-25#7275Refactor of taking container creation pieces from server to internal/factory14 comments · 2023-09-06#9969deps: replace unmaintained github.com/soheilhy/cmux11 comments · 2026-05-20
Discussions
#10544SELL CVV US/UK/CA/AU GOOD BALANCE FOR WORKING ONLINE =>TELEGRAM: @HUNG5259681 comments · 2026-11-10#10287pinns and libexec2 comments · 2026-08-29#10286pinns and setuid3 comments · 2026-08-29#9748Go 1.26 testing?1 comments · 2026-02-04#9704Process orphaned after container failure2 comments · 2026-01-09#9383How to configure a default mirror for all registries2 comments · 2025-08-05#9323Ship conmon-rs per default2 comments · 2025-07-08#9294CVE-2025-44371 comments · 2025-06-27
Latest release
v1.37.3 v1.37.3 2026-11-03CRI-O v1.37.3 The release notes have been generated for the commit range v1.37.2...v1.37.3 on Tue, 03 Nov 2026 00:21:41 UTC. Downloads Release Bundles Download one of our static release bundles via our Google Cloud Bucket. Each bundle includes a SHA-256 checksum, a cosign signature (.bundle), and a SPDX 3 bill of materials (.spdx.json) with its own signature: - cri-o.amd64.v1.37.3.tar.gz - cri-o.amd64.v1.37.3.tar.gz.sha256sum - cri-o.amd64.v1.37.3.tar.gz.bundle - cri-o.amd64.v1.37.3.tar.gz.spdx.json - cri-o.amd64.v1.37.3.tar.gz.spdx.json.bundle - cri-o.arm64.v1.37.3.tar.gz - c