liveBook · Manning

Open Container Initiative

As explained in Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more

The Open Container Initiative is an open-governance project that develops open standards for container image formats and container runtimes.

The Open Container Initiative (OCI) is an open-governance standards body for container image formats and container runtimes. It helps separate portable container artifacts from the tools that build, manage, or execute them. section 1.1

OCI runtimes configure Linux kernel features and launch containerized applications. Podman and Docker serve users directly, while runc and crun implement runtime behavior; CRI-O and containerd primarily serve Kubernetes locally. section 1.1

Figure 1.1 Different open source projects dealing with containers within the categories of orchestrators, engines, and runtimes.

Use the project-category diagram to distinguish orchestrators, container engines, and OCI runtimes. section 1.1

How Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more covers it

How deep it goes
Defines OCI and distinguishes its runtime role, but stops short of explaining the standards’ detailed specifications.
Examples
Uses Podman, Docker, runc, crun, Kata, and gVisor to illustrate engines and OCI runtime implementations.
What you can do after
Evaluate container architecture by distinguishing user-facing engines from OCI runtimes and orchestration-focused components.
How it connects
Connects OCI with Podman, Docker, Buildah, Kubernetes, containerd, CRI-O, runc, crun, Kata, and gVisor.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more. The section links point to the parts of the book it draws on.