What is the OCI and why do its specs matter?

WHAT THIS TESTS It checks whether you understand why containers from one tool run under another, and the governance that made the ecosystem interoperable rather than locked to Docker.

A GOOD ANSWER COVERS The Open Container Initiative is an open governance project under the Linux Foundation, started in 2015 with Docker donating runc. It publishes specifications, not products. The Image Format specification defines how a container image is composed: content-addressable layers, a manifest, and a config describing entrypoint and environment. The Runtime specification defines a filesystem bundle plus a config, and the lifecycle operations a compliant runtime must support to create and run a container from it. There is also a Distribution spec for registries. Because these are open, containerd, CRI-O, Podman and Kubernetes all consume the same images and call OCI-compliant runtimes, preventing vendor lock-in and enabling a plug-and-play ecosystem.

COMMON WRONG ANSWERS Saying OCI is a runtime or a daemon. Confusing it with Docker the company or the docker CLI. Believing it dictates implementation rather than defining behavior contracts.

LIKELY FOLLOW-UPS How does containerd use runc? What is a low-level versus high-level runtime? How does the Kubernetes CRI relate to OCI?

ONE CONCRETE EXAMPLE You build an image with Docker, push it to a registry following the Distribution spec, and a Kubernetes node pulls it. The kubelet talks to containerd via the CRI; containerd unpacks the OCI image bundle and invokes runc, which reads the OCI runtime config and starts the process. No Docker daemon is involved, yet everything works because each layer honors the OCI contracts.