Originally reported by devclass.com. Post date: April 9, 2020.
Docker Donates the Compose Spec to the Open-Source Community
Docker has transferred its Compose Specification to the open-source world, opening it up for community governance and actively seeking maintainers to help grow the project — particularly around cloud-native platforms like Kubernetes and Amazon Elastic Container Service (ECS).
As the project’s GitHub page states: “The Compose specification establishes a standard for the definition of multi-container platform-agnostic applications.”
What Is the Compose Specification?
Docker first launched its Compose tool in 2013 as a way to define and run multi-container Docker applications using a single YAML file. Rather than building and starting each container manually, developers declare their entire stack — services, networks, volumes — in one place and bring it up with a single docker compose up command.
The Compose Specification formalises this approach into a vendor-neutral, platform-agnostic standard. The original Docker Compose tool is listed as one implementation of this spec, leaving the door open for other tools and platforms to adopt it.
Open Governance and Industry Partners
Announcing the move, Docker senior product manager Ben De St Paer-Gotch wrote:
“This new community will be run with open governance with input from all interested parties allowing us together to create a new standard for defining multi-container apps that can be run from the desktop to the cloud.”
At the time of the announcement, the community listed on the spec’s website included Docker and Microsoft. Docker also stated it was working with Amazon Web Services (AWS), Microsoft, and others in the open-source community to extend the specification so it could more flexibly support cloud-native platforms such as Kubernetes and Amazon ECS, in addition to existing Compose platforms.
Docker also indicated its intention to submit the Compose Specification to an open-source foundation, with the goal of ensuring a level playing field and greater openness. This follows Docker’s earlier move of handing its Cloud Native Application Bundle (CNAB) technology over to the CNAB project.
Why This Matters for Developers
De St Paer-Gotch articulated the core developer value proposition clearly:
“Compose dramatically simplifies the code to cloud process and toolchain for developers by allowing them to define a complex stack in a single file and run it with a single command. This eliminates the need to build and start every container manually, saving development teams valuable time.”
By elevating Compose into a community-governed specification rather than a Docker-proprietary format, the goal is to make that simplicity available across a much broader range of platforms — from a developer’s local desktop environment all the way through to cloud-hosted Kubernetes clusters and managed container services.
Kubernetes and ECS Integration
A key motivation behind open-sourcing the spec is its expansion into Kubernetes-native workflows. Projects such as Kompose and Compose on Kubernetes already translate Compose files into Kubernetes manifests, but the spec’s new open governance model is designed to bring those efforts under a unified, standardised umbrella.
For teams that write a single docker-compose.yml file locally and want to deploy to ECS or Kubernetes in production without rewriting their configuration from scratch, a platform-agnostic spec is a significant quality-of-life improvement.
Call for Maintainers
Docker also put out a call for open-source maintainers for the project. The ideal maintainer profile, as described by De St Paer-Gotch on GitHub, is:
- Developers who actively use and rely on Compose
- Those with experience building developer tooling
- Individuals with prior experience working on open-source specifications
- Users with experience running Compose outside local development — for example, on Kubernetes (Compose on K8s), Kompose, or services like Amazon ECS
Context: Docker’s Broader Open-Source Strategy
This move followed Docker’s post-split restructuring, during which the company outlined a strategy focused on the developer experience in what it describes as the “code to cloud” lifecycle — the space between source control management (SCM) and production runtime. Docker VP of Products Justin Graham confirmed at the time that Compose, along with Notary and Docker Engine, sat firmly within the company’s open-source efforts.
Open-sourcing the Compose Specification is therefore consistent with a deliberate positioning: Docker wants Compose to be the lingua franca for defining multi-container applications, regardless of where those applications ultimately run.
Key Takeaways
- The Compose Specification is now an open, community-governed standard for defining multi-container applications.
- It is platform-agnostic: Docker Compose is one implementation, but the spec is designed to support Kubernetes, ECS, and other cloud-native platforms.
- Docker is collaborating with AWS and Microsoft to extend support for cloud-native runtimes.
- The spec may eventually be donated to an open-source foundation for neutral stewardship.
- Docker is actively seeking community maintainers with relevant experience.