Open Container Initiative-based implementation of Kubernetes Container Runtime Interface (by cri-o)


Basic cri-o repo stats
9 days ago

cri-o/cri-o is an open source project licensed under Apache License 2.0 which is an OSI approved license.

Cri-o Alternatives

Similar projects and alternatives to cri-o

  • GitHub repo containerd

    An open and reliable container runtime

  • GitHub repo kubernetes

    Production-Grade Container Scheduling and Management

  • GitHub repo jib

    🏗 Build container images for your Java applications.

  • GitHub repo kaniko

    Build Container Images In Kubernetes

  • GitHub repo runc

    CLI tool for spawning and running containers according to the OCI specification

  • GitHub repo runtime-spec

    OCI Runtime Specification

  • GitHub repo enhancements

    Enhancements tracking repo for Kubernetes

  • GitHub repo crun

    A fast and lightweight fully featured OCI runtime and C library for running containers

  • GitHub repo rules_docker

    Rules for building and handling Docker images with Bazel

  • GitHub repo distribution-spec

    OCI Distribution Specification

  • GitHub repo cri-dockerd

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better cri-o alternative or higher similarity.


Posts where cri-o has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-05-07.
  • Is Docker Dead in the Water?
    The docker utility isn't the only way to build and run containers. There's also cri-o, podman, and crun among others for running containers. For building there is podman again, Jib for Java applications, and bazel plus many others. The docker approach of using a client to connect to a daemon required to run as root has turned out to be slow and insecure.
  • Kubernetes vs Docker: Understanding Containers in 2021 | 2021-04-19
    Simply put, Docker is heavy. We get better performance with a lightweight container runtime like containerd or CRI-O. As a recent example, Google benchmarks have shown that containerd consumes less memory and CPU, and that pods start in less time than on Docker.
  • sloc cri-o vs containerd
    cri-o has containerd as dependency (for the CRI interface definition I guess) so raw cloc are kind of useless here :)
    git clone --depth 1 --branch v1.4.4 tmp-cloc-repo && \ > cloc tmp-cloc-repo && > rm -rf tmp-cloc-repo ... Language files blank comment code -------------------------------------------------------------------------------- Go 2701 76843 101820 722803 ... git clone --depth 1 --branch v1.20.2 tmp-cloc-repo && \ > cloc tmp-cloc-repo && > rm -rf tmp-cloc-repo ... Language files blank comment code -------------------------------------------------------------------------------- Go 5883 152690 209909 1401070