CRI-O
Lightweight Container Runtime for Kubernetes
CRI-O is an implementation of the Kubernetes CRI (Container Runtime Interface) to enable using OCI (Open Container Initiative) compatible runtimes. It is a lightweight alternative to using Docker as the runtime for Kubernetes. It allows Kubernetes to use any OCI-compliant runtime as the container runtime for running pods. Today it supports runc and Kata Containers as the container runtimes but any OCI-conformant runtime can be plugged in principle. CRI-O supports OCI container images and can pull from any container registry. It is a lightweight alternative to using Docker, Moby or rkt as the runtime for Kubernetes. CRI-O is developed by maintainers and contributors from Red Hat, Intel, SUSE, Hyper and IBM and others. It is a community-driven, open source project. CRI-O is a Cloud Native Computing Foundation graduated project.
7 alternatives to CRI-O
Ranked by how well each tool replaces CRI-O: shared features, audience, price and popularity.
Open source system for automating deployment, scaling, and management of containerized.
Covers 0 of 9 key features.
Free planOpen source60 out of 100 matchFreeThe Proven Development Platform for Cloud-Native Applications
Covers 0 of 9 key features.
Open source55 out of 100 match—- 54 out of 100 match—
An open framework to assemble specialized container systems without reinventing the wheel.
Covers 0 of 9 key features.
Open source52 out of 100 match—A vendor-neutral, OCI-native container image registry.
Covers 0 of 9 key features.
Open source46 out of 100 match—An open-source container management platform for releases and deployments.
Covers 0 of 9 key features.
Open source37 out of 100 match—