Docker Compose V2 Reaches General Availability
Docker Compose V2, rewritten from Python to Go and integrated into the Docker CLI as docker compose, reached general availability with new features and cloud integrations.
Historical Archive. This article documents an event from 2022 and is preserved with its original date for reference. It is not current news, and details may have changed since publication.
What happened
Docker Compose V2 reached general availability on April 26, 2022, announced on the Docker blog. The first version of Compose V2 had launched in June 2021, and after ten months of improvements and steadily increasing adoption, Docker reported that 78% of Compose users on the latest Docker Desktop were already using V2, giving the team confidence to make it generally available for production workflows.
From docker-compose to docker compose
With the GA, Compose V2 became the standard across documentation and the developer default on Docker Desktop, invoked as the docker compose subcommand rather than the standalone docker-compose. Docker Desktop 3.4 and later included Compose V2 automatically, and versions 4.4.2 and later aliased the docker-compose syntax to docker compose by default, letting V2 serve as a drop-in replacement with minimal script changes. Compose V1 was marked deprecated, receiving only high-priority security and critical bug fixes.
Rewritten in Go
A central change was that Compose V2 was completely rewritten from Python to Go, making it consistent with the rest of the Docker ecosystem. This let the team vendor code from Moby and the Docker CLI, share functions such as the run and exec implementations across Compose and the CLI for consistent behaviour, and ship a static binary that avoided Python packaging and dependency-management problems while enabling cross-compilation and faster native execution.
New features and cloud integrations
The transition to Go let Docker deliver new features faster within the CLI, including GPU device reservations, profiles for selectively enabling services, docker compose ls to list Compose apps, and docker compose cp to copy files. Compose V2 also introduced a path to production through the Compose specification and cloud integrations, letting developers deploy Compose applications to Amazon ECS or Microsoft ACI by switching the Docker context, and to run commands using a project name without the original Compose file present.
Why it mattered
Compose V2 unified one of Docker's most-used tools with the rest of its Go-based ecosystem, enabling a faster feature cadence and a more consistent experience. Folding Compose into the Docker CLI as docker compose, with cloud deployment paths and static binaries, modernised a workflow that millions of developers rely on daily.
Related on Skillo
See also: Docker Desktop for Linux reaches GA.
Sources
Published date reflects the original event date (2022-04-26). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.
Written by
Skillo Staff
0 Comments
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.