Docker open sources critical infrastructure component “containerd”, cloud vendors including Alibaba, AWS, Google, IBM, and Microsoft sign on to work on it
Docker announced today that it was open sourcing containerd (pronounced Container D), making a key infrastructure piece …
Context & Ripple Effects
This move completes an arc that started when rival CoreOS spun its App Container project into a separate foundation with Google, VMware, Red Hat, and Apcera backing, and when Docker joined those same rivals under the Linux Foundation-backed Open Container Project to defuse standards fights. Since then Docker has been pulling more function into its own product, notably building orchestration directly into Docker Engine in mid-2016.
Open sourcing containerd with Alibaba, AWS, Google, IBM, and Microsoft as contributors is the counterweight: Docker hands the lowest runtime layer to the ecosystem it depends on, buying back trust for the layers it intends to keep selling.
First-order effects
- The five sign-on cloud vendors gain direct influence over the container runtime their own container services are built on, ending Docker's sole-control position over a component they all rely on.
- Docker gives up exclusive stewardship of containerd immediately, trading control of the base layer for credibility after the orchestration-in-Engine move raised single-vendor concerns.
Second-order effects
- Alternative runtimes from the CoreOS lineage now face pressure to converge on containerd rather than sustain forks, since the major clouds have thrown weight behind one shared implementation.
- Docker's differentiation shifts up-stack toward paid packaging — a direction its later Enterprise Edition makes explicit by bundling a runtime, orchestration, security, and management for corporate buyers.
Third-order effects
- If the pattern holds, container infrastructure stratifies into a commons-governed base layer with commercial competition concentrated in orchestration and management above it — extending the OCI standards work from paper specs into shared code.
- Vendors that commoditize the layer beneath them set a template other infrastructure companies can follow when platform customers demand neutrality.
The trend: Critical container infrastructure is migrating from single-vendor ownership toward foundation-style shared stewardship, pushing commercial competition up the stack.