June 22, 2015

Open Container Initiative launched

DockerSoftware that packages applications into containers — became the default way to ship and deploy services., CoreOS, and others launched the OCI on June 22, 2015 — an open standardA specification anyone can implement without proprietary restrictions — encourages interoperability and competition. for containerAn isolated runtime environment packaging an app and its dependencies — lighter than full virtual machines. image formats and runtimes, donating runc as the reference implementation.

What it was for

Docker (software)OCI specs define how containerAn isolated runtime environment packaging an app and its dependencies — lighter than full virtual machines. images are built, stored, and executed — image manifest, runtime bundle, and registry distribution. runc implements the runtime spec; containerd, CRI-O, and Podman build on it. Example: a `docker pull` image conforms to OCI Image Format; `runc run` starts it per OCI Runtime Spec.

Companies

  • Docker

Why it's here

OCI prevented containerAn isolated runtime environment packaging an app and its dependencies — lighter than full virtual machines. formats from fragmenting into incompatible vendor silos.

Why it mattered

It let KubernetesAn orchestration system for containers — schedules, scales, and manages fleets of services in production., Podman, and DockerSoftware that packages applications into containers — became the default way to ship and deploy services. share images and runtime semantics.

What it solved

The containerAn isolated runtime environment packaging an app and its dependencies — lighter than full virtual machines. ecosystem needed vendor-neutral standards before proprietary formats locked in users.

Media

  • Docker (software)
    ImageDocker (software)

    Kopiersperre (talk), Public domain, via Wikimedia Commons

Related