1.15.0
If you're a Mac or Windows user, the best way to install Compose and keep it up-to-date is Docker for Mac and Windows.
Docker for Mac and Windows will automatically install the latest version of Docker Engine for you.
Alternatively, you can use the usual commands to install or upgrade Compose:
curl -L https://github.com/docker/compose/releases/download/1.15.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
See the install docs for more install options and instructions.
Compose file format compatibility matrix
| Compose file format | Docker Engine |
|---|---|
| 3.3 | 17.06.0+ |
| 3.0 – 3.2 | 1.13.0+ |
| 2.2 | 1.13.0+ |
| 2.1 | 1.12.0+ |
| 2.0 | 1.10.0+ |
| 1.0 | 1.9.1+ |
Changes
New features
Compose file version 2.2
- Added support for the
networkparameter in build configurations.
Compose file version 2.1 and up
-
The
pidoption in a service's definition now supports aservice:<name>
value. -
Added support for the
storage_optparameter in in service definitions.
This option is not available for the v3 format
All formats
-
Added
--quietflag todocker-compose pull, suppressing progress output -
Some improvements to CLI output
Bugfixes
-
Volumes specified through the
--volumeflag ofdocker-compose runnow
complement volumes declared in the service's defintion instead of replacing
them -
Fixed a bug where using multiple Compose files would unset the scale value
defined inside the Compose file. -
Fixed an issue where the
credHelpersentries in theconfig.jsonfile
were not being honored by Compose -
Fixed a bug where using multiple Compose files with port declarations
would cause failures in Python 3 environments -
Fixed a bug where some proxy-related options present in the user's
environment would prevent Compose from running -
Fixed an issue where the output of
docker-compose configwould be invalid
if the original file usedYorNvalues -
Fixed an issue preventing
upoperations on a previously created stack on
Windows Engine.
Thanks to @AlexeyRokhin, @edsrzf, @NikitaVlaznev, @jbarciauskas, @thaJeztah, @protoss-player, @kirinrastogi, @IPv4v6, @Dineshs91, @ColinHebert and @andyneff for contributing to this release!