Table of Contents
Foundation
OCI: Open Container Initiativefounded by Docker, CoreOS, and othersimage-specruntime-specCRI: Container Runtime Interface enables kubelet to use different runtimesCNI: Container Network Interface
Container Runtimes
high-level runtimes often incorporate low-level runtimes that are otherwise standalone projects.
If tomorrow you get the urge to add your own container project to the ever-growing jungle, you should make it OCI-, CRI- and CNI-compliant



runc = libcontainer + ..runc runs OCI open container image directly(high level) rkt (obsolete) did not rely on daemonlxc: virtual env that does not emulate the hardware. he focus of Linux Containers are base images (e. g. Ubuntu) rather than application-tailored images.singularity focuses on High Performance Computing. Uses Singularity Image Format (SIF), but also supports OCI/CRI
VM-like Container Runtimes


**Firecracker**Amazon project, FaaS, VMM that uses KVM to create microVM.Efforts:
- Firecracker instead of QEMU as VMM for Kata Containers
- firecracker-containerd mapper allows containerd to run containers as microVMs
**gVisor**Google, runsc, OCI compilant, Sentry, GoferSentry is the central user-space OS kernel that the untrusted application uses.Not every system call, /proc or /sys file is implemented.
**Source: **
and other opensource sites.