As a Docker user, you might have come across two different commands to spin up your containers: docker-compose up and docker compose up. But what’s the difference between them? And which one should you use? In this article, we’ll delve into the history and development of Docker Compose, explore the differences between Compose V1 and Compose V2, and provide guidance on which command to use.

A Brief History of Docker Compose

Docker Compose was first introduced in 2014 as a tool for defining and running multi-container Docker applications. The initial version, Compose V1, was written in Python and used the docker-compose command. Over the years, Compose V1 underwent several updates, with the last major version being 3.8 in 2020. This marks the end of the “docker-compose” era, and it’s time to move on to the newer and better “docker compose” method.

In 2020, Docker announced the release of Compose V2, written in Go, which introduced a new command: docker compose. This new version aimed to simplify the Compose experience, improve performance, and provide a more consistent user interface.

Compose File Format Versioning

Compose V1 used three major file format versions: 1, 2.x, and 3.x. Each version introduced new features and improvements, with the 3.x format being the most recent. However, the multiple file formats led to confusion, and the versioning system became cumbersome.

Compose V2 introduced the Compose Specification, a rolling format that replaces the traditional versioning system. This new format makes the version top-level element optional and introduces optional specifications for Deploy, Develop, and Build.

Key Differences between Compose V1 and Compose V2

So, what are the main differences between Compose V1 and Compose V2?

• Command: Compose V1 uses docker-compose, while Compose V2 uses docker compose.
• File format: Compose V1 uses the traditional versioned file format (2.x, 3.x), while Compose V2 uses the Compose Specification.
• Versioning: Compose V1 requires a specific version element in the compose.yml file, while Compose V2 ignores this element.
• Backwards compatibility: Compose V2 provides backwards compatibility for certain deprecated or changed elements between Compose file format 2.x/3.x and the Compose Specification.

Switch to “docker compose up” Today!

If you’re still using docker-compose up, it’s time to switch to docker compose up. The docker-compose method is no longer maintained or updated, and you might miss out on new features and security patches. With docker compose up, you’ll get a more streamlined experience, improved performance, and a more consistent user interface.

In conclusion, it’s time to bid farewell to docker-compose up and hello to docker compose up. Make the switch today and take advantage of the latest features and improvements that Docker Compose has to offer.