CRI-O - OCI-based implementation of Kubernetes Container Runtime Interface

Compatibility matrix: CRI-O ⬄ Kubernetes

CRI-O follows the Kubernetes release cycles with respect to its minor versions(1.x.0). Patch releases (1.x.y) for CRI-O are not in sync with those fromKubernetes, because those are scheduled for each month, whereas CRI-O providesthem only if necessary. If a Kubernetes release goes End ofLife,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 skewpolicy when it comes to feature graduation, deprecation or removal. This alsoapplies to features which are independent from Kubernetes.

For more information visit the Kubernetes versioningdocumentation.

Key:

• ✓ Changes in main Kubernetes repo about CRI are actively implemented in CRI-O
• = Maintenance is manual, only bugs will be patched.

The release notes for CRI-O are hand-crafted and can be continuously retrievedfrom 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 image management (managing image layers, overlay filesystems, etc)
• Container process lifecycle management
• Monitoring and logging required to satisfy the CRI
• Resource isolation as required by the CRI

What is not in scope for this project?

• Building, signing and pushing images to various image storages
• A CLI utility for interacting with CRI-O. Any CLIs built as part of this project are only meant for testing this project and there will be no guarantees on the backward compatibility with it.

This is an implementation of the Kubernetes Container Runtime Interface (CRI) that will allow Kubernetes to directly launch and manage Open Container Initiative (OCI) containers.

The plan is to use OCI projects and best of breed libraries for different aspects:

• Runtime: runc (or any OCI runtime-spec implementation) and oci runtime tools
• Images: Image management using containers/image
• Storage: Storage and management of image layers using containers/storage
• Networking: Networking support through use of CNI

It is currently in active development in the Kubernetes community through the design proposal. Questions and issues should be raised in the Kubernetes sig-node Slack channel.

Commands

Note that kpod and its container management and debugging commands have moved to a separate repository, located here.

Configuration

OCI Hooks Support

You can configure CRI-O to inject OCI Hooks when creating containers.

CRI-O Usage Transfer

We provide useful information for operations and development transfer as it relates to infrastructure that utilizes CRI-O.

Communication

For async communication and long running discussions please use issues and pull requests on the github repo. This will be the best place to discuss design and implementation.

For chat communication we have a channel on the Kubernetes slack that everyone is welcome to join and chat about development.

Awesome CRI-O

We maintain a curated list of links related to CRI-O. Did you findsomething interesting on the web about the project? Awesome, feel free to openup a PR and add it to the list.

Getting started

Installing CRI-O

To install CRI-O, you can follow our installation guide.Alternatively, if you'd rather build CRI-O from source, checkout our setupguide.We also provide a way in building static binaries of CRI-O via nix.Those binaries are available for every successfully built commit on our Google Cloud Storage Bucket.This means that the latest commit can be installed via our convinience script:

> curl https://raw.githubusercontent.com/cri-o/cri-o/main/scripts/get | bash

Beside amd64 we also support the arm64 bit architecture. This can beselected via the script, too:

> curl https://raw.githubusercontent.com/cri-o/cri-o/main/scripts/get | bash -s -- -a arm64

It is also possible to select a specific git SHA or tag by:

> curl https://raw.githubusercontent.com/cri-o/cri-o/main/scripts/get | bash -s -- -t v1.21.0

The above script resolves to the download URL of the static binary bundletarball matching the format:

https://storage.googleapis.com/cri-o/artifacts/cri-o.$ARCH.$REV.tar.gz

where $ARCH can be amd64 or arm64 and $REV can be any git SHA or tag.Please be aware that using the latest master SHA might cause a race, becausethe CI has not finished publishing the artifacts yet or failed.

Running kubernetes with CRI-O

Before you begin, you'll need to start CRI-O

You can run a local version of Kubernetes with CRI-O using local-up-cluster.sh:

1. Clone the Kubernetes repository
2. From the Kubernetes project directory, run:

CGROUP_DRIVER=systemd \
CONTAINER_RUNTIME=remote \
CONTAINER_RUNTIME_ENDPOINT='unix:///var/run/crio/crio.sock' \
./hack/local-up-cluster.sh

For more guidance in running CRI-O, visit our tutorial page

The HTTP status API

CRI-O exposes per default the gRPC API to fulfill theContainer Runtime Interface (CRI) of Kubernetes. Besides this, there exists anadditional HTTP API to retrieve further runtime status information about CRI-O.Please be aware that this API is not considered to be stable and productionuse-cases should not rely on it.

On a running CRI-O instance, we can access the API via an HTTP transfer tool likecurl:

$ sudo curl -v --unix-socket /var/run/crio/crio.sock http://localhost/info | jq
{
  "storage_driver": "btrfs",
  "storage_root": "/var/lib/containers/storage",
  "cgroup_driver": "systemd",
  "default_id_mappings": { ... }
}

The following API entry points are currently supported:

The tool crio-status can be used to access the API with a dedicated commandline tool. It supports all API endpoints via the dedicated subcommands config,info and containers, for example:

$ sudo go run cmd/crio-status/main.go info
cgroup driver: systemd
storage driver: btrfs
storage root: /var/lib/containers/storage
default GID mappings (format <container>:<host>:<size>):
  0:0:4294967295
default UID mappings (format <container>:<host>:<size>):
  0:0:4294967295

Metrics

Please refer to the CRI-O Metrics guide.

Container Runtime Interface special cases

Some aspects of the Container Runtime are worth some additional explanation.These details are summarized in a dedicated guide.

Debugging tips

Having an issue? There are some tips and tricks for debugging located in our debugging guide

Adopters

An incomplete list of adopters of CRI-O in production environments can be found here.If you're a user, please help us complete it by submitting a pull-request!

Weekly Meeting

A weekly meeting is held to discuss CRI-O development. It is open to everyone.The details to join the meeting are on the wiki.

License Scan