1.5.0 RC1

This is a release candidate for version 1.5.0 of Compose.

Note that Compose 1.5.0 requires Docker 1.8.0 or later.

To try it out, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.5.0rc1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.5.0rc1 if you prefer pip.

Here's what's new:

---

Major Features

• Compose is now available on windows.
• Environment variable can be used in the compose file. See
  https://github.com/docker/compose/blob/129092b7/docs/yml.md#variable-substitution
• Multiple compose files can be specified, allowing you to override
  setting in the default compose file. See
  https://github.com/docker/compose/blob/129092b7/docs/reference/docker-compose.md
  for more details.
• Configuration validation is now a lot more strict
• up now waits for all services to exit before shutting down
• Support for the new docker networking can be enabled with
  the --x-networking flag

New Features

• volumes_from now supports a mode option allowing for read-only
  volumes_from
• Volumes that don't start with a path indicator (. or /) will now be
  treated as a named volume. Previously this was a warning.
• --pull flag added to build
• --ignore-pull-failures flag added to pull
• Support for the ipc field added to the compose file
• Containers created by run can now be named with the --name flag
• If you install Compose with pip or use it as a library, it now
  works with Python 3
• image field now supports image digests (in addition to ids and tags)
• ports now supports ranges of ports
• --publish flag added to run
• New subcommands pause and unpause
• services may be extended from the same file without a file key in
  extends
• Compose can be installed and run as a docker image. This is an experimental
  feature.

Bug Fixes

• Support all log_drivers
• Fixed build when running against swarm
• ~ is no longer expanded on the host when included as part of a container
  volume path

Thanks @aanand, @mnowster, @moxiegirl, @mrfuxi, @shin-, @bfirsh, @albers @funkyfuture, @uvgroovy, @predakanga, @charleswhchan, @ggtools, and everyone else who contributed to this release!

1.4.2

Firstly, note that Compose 1.4.2 requires Docker 1.7.0 or later.

Secondly, if you're a Mac user, the Docker Toolbox will install Compose 1.4.2 for you, alongside the latest versions of the Docker Engine, Machine and Kitematic.

Otherwise, you can use the usual commands to install/upgrade. Either download the binary:

curl -L https://github.com/docker/compose/releases/download/1.4.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or install the PyPi package:

pip install -U docker-compose==1.4.2

This release fixes a regression in the 1.4.1 release that would cause docker-compose up without the -d option to exit immediately.

1.4.1

Firstly, note that Compose 1.4.1 requires Docker 1.7.0 or later.

Secondly, if you're a Mac user, the Docker Toolbox will install Compose 1.4.1 for you, alongside the latest versions of the Docker Engine, Machine and Kitematic.

Otherwise, you can use the usual commands to install/upgrade. Either download the binary:

curl -L https://github.com/docker/compose/releases/download/1.4.1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or install the PyPi package:

pip install -U docker-compose==1.4.1

The following issues were fixed in this release:

• Some configuration changes (notably changes to links, volumes_from, and
  net) were not properly triggering a container recreate as part of
  docker-compose up.
• docker-compose up <service> was showing logs for all services instead of
  just the specified services.
• Containers with custom container names were showing up in logs as
  service_number instead of their custom container name.
• When scaling a service sometimes containers would be recreated even when
  the configuration had not changed.

1.4.0

Firstly, note that Compose 1.4.0 requires Docker 1.7.1 or later.

Secondly, if you're a Mac user, the Docker Toolbox will install Compose 1.4.0 for you, alongside the latest versions of the Docker Engine, Machine and Kitematic.

Otherwise, you can use the usual commands to install/upgrade. Either download the binary:

curl -L https://github.com/docker/compose/releases/download/1.4.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or install the PyPi package:

pip install -U docker-compose==1.4.0

Here's what's new:

• By default, docker-compose up now only recreates containers for services whose configuration has changed since they were created. This should result in a dramatic speed-up for many applications.

The experimental --x-smart-recreate flag which introduced this feature in Compose 1.3.0 has been removed, and a --force-recreate flag has been added for when you want to recreate everything.

• Several of Compose's commands - scale, stop, kill and rm - now perform actions on multiple containers in parallel, rather than in sequence, which will run much faster on larger applications.
• You can now specify a custom name for a service's container with container_name. Because Docker container names must be unique, this means you can't scale the service beyond one container.
• You no longer have to specify a file option when using extends - it will default to the current file.
• Service names can now contain dots, dashes and underscores.
• Compose can now read YAML configuration from standard input, rather than from a file, by specifying - as the filename. This makes it easier to generate configuration dynamically:

$ echo 'redis: {"image": "redis"}' | docker-compose --file - up

• There's a new docker-compose version command which prints extended information about Compose's bundled dependencies.
• docker-compose.yml now supports log_opt as well as log_driver, allowing you to pass extra configuration to a service's logging driver.
• docker-compose.yml now supports memswap_limit, similar to docker run --memory-swap.
• When mounting volumes with the volumes option, you can now pass in any mode supported by the daemon, not just :ro or :rw. For example, SELinux users can pass :z or :Z.
• You can now specify a custom volume driver with the volume_driver option in docker-compose.yml, much like docker run --volume-driver.
• A bug has been fixed where Compose would fail to pull images from private registries serving plain (unsecured) HTTP. The --allow-insecure-ssl flag, which was previously used to work around this issue, has been deprecated and now has no effect.
• A bug has been fixed where docker-compose build would fail if the build depended on a private Hub image or an image from a private registry.
• A bug has been fixed where Compose would crash if there were containers which the Docker daemon had not finished removing.
• Two bugs have been fixed where Compose would sometimes fail with a "Duplicate bind mount" error, or fail to attach volumes to a container, if there was a volume path specified in docker-compose.yml with a trailing slash.

Thanks @mnowster, @dnephin, @ekristen, @funkyfuture, @jeffk and @lukemarsden!

1.4.0 RC3

This is a release candidate for version 1.4.0 of Compose. To try it out, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.4.0rc3/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.4.0rc3 if you prefer Pip.

On top of the changes in RC1 and RC2, this release contains the following changes:

• You can now specify a custom volume driver with the volume_driver option in docker-compose.yml, much like docker run --volume-driver.
• Two bugs have been fixed where Compose would sometimes fail with a "Duplicate bind mount" error, or fail to attach volumes to a container, if there was a volume path specified in docker-compose.yml with a trailing slash.
• Fixed a bug where docker-compose build would fail if the build depended on a private Hub image or an image from a private registry.

Here are the most important changes in 1.4.0:

• By default, docker-compose up now only recreates containers for services whose configuration has changed since they were created. This should result in a dramatic speed-up for many applications.

The experimental --x-smart-recreate flag which introduced this feature in Compose 1.3.0 has been removed, and a --force-recreate flag has been added for when you want to recreate everything.

• Several of Compose's commands - scale, stop, kill and rm - now perform actions on multiple containers in parallel, rather than in sequence, which will run much faster on larger applications.
• You can now specify a custom name for a service's container with container_name. Because Docker container names must be unique, this means you can't scale the service beyond one container.
• You no longer have to specify a file option when using extends - it will default to the current file.
• Service names can now contain dots, dashes and underscores.
• Compose can now read YAML configuration from standard input, rather than from a file, by specifying - as the filename. This makes it easier to generate configuration dynamically:

$ echo 'redis: {"image": "redis"}' | docker-compose --file - up

• There's a new docker-compose version command which prints extended information about Compose's bundled dependencies.
• docker-compose.yml now supports log_opt as well as log_driver, allowing you to pass extra configuration to a service's logging driver.
• docker-compose.yml now supports memswap_limit, similar to docker run --memory-swap.
• When mounting volumes with the volumes option, you can now pass in any mode supported by the daemon, not just :ro or :rw. For example, SELinux users can pass :z or :Z.

1.4.0 RC2

This is a release candidate for version 1.4.0 of Compose. To try it out, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.4.0rc2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.4.0rc2 if you prefer Pip.

On top of the changes in RC1, the following bugs have been fixed:

• A bug has been fixed where Compose would fail to pull images from private registries serving plain (unsecured) HTTP. The --allow-insecure-ssl flag, which was previously used to work around this issue, has been deprecated and now has no effect.
• A regression has been fixed where specifying a custom container name for a service with container_name would cause docker-compose run to fail for that service.

Here are the most important changes in 1.4.0:

• By default, docker-compose up now only recreates containers for services whose configuration has changed since they were created. This should result in a dramatic speed-up for many applications.

The experimental --x-smart-recreate flag which introduced this feature in Compose 1.3.0 has been removed, and a --force-recreate flag has been added for when you want to recreate everything.

• Several of Compose's commands - scale, stop, kill and rm - now perform actions on multiple containers in parallel, rather than in sequence, which will run much faster on larger applications.
• You can now specify a custom name for a service's container with container_name. Because Docker container names must be unique, this means you can't scale the service beyond one container.
• You no longer have to specify a file option when using extends - it will default to the current file.
• Service names can now contain dots, dashes and underscores.
• Compose can now read YAML configuration from standard input, rather than from a file, by specifying - as the filename. This makes it easier to generate configuration dynamically:

$ echo 'redis: {"image": "redis"}' | docker-compose --file - up

• There's a new docker-compose version command which prints extended information about Compose's bundled dependencies.
• docker-compose.yml now supports log_opt as well as log_driver, allowing you to pass extra configuration to a service's logging driver.
• docker-compose.yml now supports memswap_limit, similar to docker run --memory-swap.
• When mounting volumes with the volumes option, you can now pass in any mode supported by the daemon, not just :ro or :rw. For example, SELinux users can pass :z or :Z.

Thanks @dnephin, @ekristen, @funkyfuture, @jeffk and @mnowster!

1.4.0 RC1

This is a release candidate for version 1.4.0 of Compose. To try it out, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.4.0rc1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.4.0rc1 if you prefer Pip.

Here are the most important changes in 1.4.0:

• By default, docker-compose up now only recreates containers for services whose configuration has changed since they were created. This should result in a dramatic speed-up for many applications.

The experimental --x-smart-recreate flag which introduced this feature in Compose 1.3.0 has been removed, and a --force-recreate flag has been added for when you want to recreate everything.

• Several of Compose's commands - scale, stop, kill and rm - now perform actions on multiple containers in parallel, rather than in sequence, which will run much faster on larger applications.
• You can now specify a custom name for a service's container with container_name. Because Docker container names must be unique, this means you can't scale the service beyond one container.
• You no longer have to specify a file option when using extends - it will default to the current file.
• Service names can now contain dots, dashes and underscores.
• Compose can now read YAML configuration from standard input, rather than from a file, by specifying - as the filename. This makes it easier to generate configuration dynamically:

$ echo 'redis: {"image": "redis"}' | docker-compose --file - up

• There's a new docker-compose version command which prints extended information about Compose's bundled dependencies.
• docker-compose.yml now supports log_opt as well as log_driver, allowing you to pass extra configuration to a service's logging driver.
• docker-compose.yml now supports memswap_limit, similar to docker run --memory-swap.
• When mounting volumes with the volumes option, you can now pass in any mode supported by the daemon, not just :ro or :rw. For example, SELinux users can pass :z or :Z.

Thanks @dnephin, @ekristen, @funkyfuture, @jeffk and @mnowster!

1.3.3

If you're upgrading from Compose 1.2.0 or earlier, this release contains breaking changes - be sure to read the 1.3.0 release notes.

To install Compose 1.3.3, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.3.3/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.3.3 if you prefer Pip.

Two regressions have been fixed:

• When stopping containers gracefully, Compose was setting the timeout to 0, effectively forcing a SIGKILL every time.
• Compose would sometimes crash depending on the formatting of container data returned from the Docker API.

1.3.2

If you're upgrading from Compose 1.2.0 or earlier, this release contains breaking changes - be sure to read the 1.3.0 release notes.

To install Compose 1.3.2, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.3.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.3.2 if you prefer Pip.

The following bugs have been fixed:

• When there were one-off containers created by running docker-compose run on an older version of Compose, docker-compose run would fail with a name collision. Compose now shows an error if you have leftover containers of this type lying around, and tells you how to remove them.
• Compose was not reading Docker authentication config files created in the new location, ~/docker/config.json, and authentication against private registries would therefore fail.
• When a container had a pseudo-TTY attached, its output in docker-compose up would be truncated.
• docker-compose up --x-smart-recreate would sometimes fail when an image tag was updated.
• docker-compose up would sometimes create two containers with the same numeric suffix.
• docker-compose rm and docker-compose ps would sometimes list services that aren't part of the current project (though no containers were erroneously removed).
• Some docker-compose commands would not show an error if invalid service names were passed in.

Thanks @dano, @josephpage, @kevinsimper, @lieryan, @phemmer, @soulrebel and @sschepens!

1.3.1

If you're upgrading from Compose 1.2.0 or earlier, this release contains breaking changes - be sure to read the 1.3.0 release notes.

To install Compose 1.3.1, run the following commands:

curl -L https://github.com/docker/compose/releases/download/1.3.1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Or pip install -U docker-compose==1.3.1 if you prefer Pip.

The following bugs have been fixed:

• docker-compose build would always attempt to pull the base image before building.
• docker-compose help migrate-to-labels failed with an error.
• If no network mode was specified, Compose would set it to "bridge", rather than allowing the Docker daemon to use its configured default network mode.