Moby is an OCI container engine and runtime manager designed for building, running, and managing isolated containers based on Open Container Initiative standards. It functions as a container daemon and image builder, providing a core engine to orchestrate the full lifecycle of containers and the packaging of source code into portable images. The project provides a standardized HTTP interface that allows for programmatic container management, enabling external clients to control daemon settings and container operations. It supports a rootless security model, allowing the engine daemon to execu
Incus is a unified orchestration platform for managing system containers, OCI application containers, and virtual machines through a single control plane. It brings together cluster infrastructure management, secure multi-tenancy, software-defined networking, and pluggable storage backend orchestration into one cohesive system exposed via a full REST API and command-line interface. What distinguishes Incus is its ability to run multiple instance types side by side—full Linux system containers, OCI application containers, and QEMU virtual machines—all managed with consistent tooling. Networkin
Buildkit is a programmable container build toolkit and OCI container image builder that converts build definitions into concurrent dependency graphs for image construction. It functions as an OCI image distribution engine, capable of generating container images and exporting artifacts to local storage or remote registries. The project is distinguished by its use of a low-level binary intermediate representation to decouple high-level build languages from the execution engine. It supports multi-platform image builds through user-mode architecture emulation and provides a distributed build cach
crun is a low-level container runtime that implements the Open Container Initiative specification for managing the lifecycle of isolated processes. It provides the core mechanisms for container creation, execution, and deletion, ensuring compatibility across platforms through standardized lifecycle management. The project distinguishes itself by offering a shared C library that allows container runtime operations to be embedded directly into other compiled applications. It further extends execution capabilities through specialized handlers that enable the deployment of containers within isola
CRI-O is an open-source container runtime that implements the Kubernetes Container Runtime Interface (CRI) to manage container images, pods, and containers on cluster nodes using OCI-compatible runtimes. It serves as a node-level container manager that handles image pulling, container lifecycle, and resource monitoring for Kubernetes clusters, running containers according to the Open Container Initiative specifications.
Las características principales de cri-o/cri-o son: Container Runtime Interfaces, Container Lifecycle Management, Container Lifecycle Automation, CNI Plugin Integrations, CNI Plugin Health Monitors, Container Command Execution, CDI Device Resolutions, Pod Lifecycle Managements.
Las alternativas de código abierto para cri-o/cri-o incluyen: moby/moby — Moby is an OCI container engine and runtime manager designed for building, running, and managing isolated containers… lxc/incus — Incus is a unified orchestration platform for managing system containers, OCI application containers, and virtual… moby/buildkit — Buildkit is a programmable container build toolkit and OCI container image builder that converts build definitions… containers/crun — crun is a low-level container runtime that implements the Open Container Initiative specification for managing the… youki-dev/youki — Youki is a low-level container runtime written in Rust that creates and manages isolated containers according to Open… containerd/containerd — Containerd is a daemon-based container runtime that manages the complete lifecycle of containers on a host system. It…