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:/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:/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.

1.3.0

To install Compose 1.3.0, run the following commands:

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

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

Optionally, you can also install command completion for bash or zsh.

Firstly, two important notes:

• This release contains breaking changes, and you will need to either remove or migrate your existing containers before running your app - see the upgrading section of the install docs for details.
• Compose now requires Docker 1.6.0 or later.

We've done a lot of work in this release to remove hacks and make Compose more stable:

• Compose now uses container labels, rather than names, to keep track of containers. This makes Compose both faster and easier to integrate with your own tools.
• Compose no longer uses "intermediate containers" when recreating containers for a service. This makes docker-compose up less complex and more resilient to failure.

There are some new features:

• docker-compose up has an experimental new behaviour: it will only recreate containers for services whose configuration has changed in docker-compose.yml. This will eventually become the default, but for now you can take it for a spin:

  $ docker-compose up --x-smart-recreate
  

• When invoked in a subdirectory of a project, docker-compose will now climb up through parent directories until it finds a docker-compose.yml.

Several new configuration keys have been added to docker-compose.yml:

• dockerfile, like docker build --file, lets you specify an alternate Dockerfile to use with build.
• labels, like docker run --labels, lets you add custom metadata to containers.
• extra_hosts, like docker run --add-host, lets you add entries to a container's /etc/hosts file.
• pid: host, like docker run --pid=host, lets you reuse the same PID namespace as the host machine.
• cpuset, like docker run --cpuset-cpus, lets you specify which CPUs to allow execution in.
• read_only, like docker run --read-only, lets you mount a container's filesystem as read-only.
• security_opt, like docker run --security-opt, lets you specify security options.
• log_driver, like docker run --log-driver, lets you specify a log driver.

Many bugs have been fixed, including the following:

• The output of docker-compose run was sometimes truncated, especially when running under Jenkins.
• A service's volumes would sometimes not update after volume configuration was changed in docker-compose.yml.
• Authenticating against third-party registries would sometimes fail.
• docker-compose run --rm would fail to remove the container if the service had a restart policy in place.
• docker-compose scale would refuse to scale a service beyond 1 container if it exposed a specific port number on the host.
• Compose would refuse to create multiple volume entries with the same host path.

Thanks @ahromis, @albers, @aleksandr-vin, @antoineco, @ccverak, @chernjie, @dnephin, @edmorley, @fordhurley, @josephpage, @KyleJamesWalker, @lsowen, @mchasal, @noironetworks, @sdake, @sdurrheimer, @sherter, @stephenlawrence, @thaJeztah, @thieman, @turtlemonvh, @twhiteman, @vdemeester, @xuxinkun and @zwily!

1.3.0 RC3

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

curl -L https:/docker/compose/releases/download/1.3.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.3.0rc3 if you prefer Pip.

This release contains breaking changes, and you will need to either remove or migrate your existing containers before running your app - see the upgrading section of the install docs for details.

There are lots of new things in 1.3 - have a look at the RC1 changelog for details.

On top of RC2, several bugs have been fixed:

• docker-compose scale would refuse to scale a service beyond 1 container if it exposed a specific port number on the host.
• Container creation would sometimes fail with a "Duplicate volume" error.
• Compose would refuse to create multiple volume entries with the same host path.

1.3.0 RC2

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

curl -L https:/docker/compose/releases/download/1.3.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.3.0rc2 if you prefer Pip.

This release contains breaking changes, and you will need to either remove or migrate your existing containers before running your app - see the upgrading section of the install docs for details.

There are lots of new things in 1.3 - have a look at the RC1 changelog for details.

In this RC, several bugs have been fixed:

• SSL certificate verification would sometimes fail.
• docker-compose run --rm was not removing the container when finished.
• docker-compose up was printing duplicate log messages when recreating containers.

1.3.0 RC1

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

curl -L https:/docker/compose/releases/download/1.3.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.3.0rc1 if you prefer Pip.

Now, two important notes:

• This release contains breaking changes, and you will need to either remove or migrate your existing containers before running your app - see the upgrading section of the install docs for details.
• Compose now requires Docker 1.6.0 or later.

We've done a lot of work in this release to remove hacks and make Compose more stable:

• Compose now uses Docker labels, rather than container names, to keep track of containers. This is both cleaner and more performant.
• Compose no longer uses "intermediate containers" when recreating containers for a service. This makes docker-compose up less complex and more resilient to failure.

There are some new features:

• docker-compose up has an experimental new behaviour: it will only recreate containers for services whose configuration has changed in docker-compose.yml. This will eventually become the default, but for now you can take it for a spin:

  $ docker-compose up --x-smart-recreate
  

• When invoked in a subdirectory of a project, docker-compose will now climb up through parent directories until it finds a docker-compose.yml.

Several new configuration keys have been added to docker-compose.yml:

• dockerfile, like docker build --file, lets you specify an alternate Dockerfile to use with build.
• labels, like docker run --labels, lets you add custom metadata to containers.
• extra_hosts, like docker run --add-host, lets you add entries to a container's /etc/hosts file.
• pid: host, like docker run --pid=host, lets you reuse the same PID namespace as the host machine.
• cpuset, like docker run --cpuset-cpus, lets you specify which CPUs to allow execution in.
• read_only, like docker run --read-only, lets you mount a container's filesystem as read-only.
• security_opt, like docker run --security-opt, lets you specify security options.
• log_driver, like docker run --log-driver, lets you specify a log driver.

Many bugs have been fixed, including the following:

• The output of docker-compose run was sometimes truncated, especially when running under Jenkins.
• A service's volumes would sometimes not update after volume configuration was changed in docker-compose.yml.
• Authenticating against third-party registries would sometimes fail.
• docker-compose run --rm would fail to remove the container if the service had a restart policy in place.

Thanks @ahromis, @albers, @aleksandr-vin, @antoineco, @ccverak, @chernjie, @dnephin, @josephpage, @KyleJamesWalker, @lsowen, @mchasal, @sdake, @sherter, @stephenlawrence, @turtlemonvh, @vdemeester, @xuxinkun and @zwily!

1.2.0

To install Compose 1.2.0, run the following commands:

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

Optionally, you can also install command completion for the bash shell.

Here's what's new:

• docker-compose.yml now supports an extends option, which enables a service to inherit configuration from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the documentation.
• When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use build.
• Repeated invocations of docker-compose up when using Compose with a Swarm cluster now work reliably.
• Directories passed to build, filenames passed to env_file and volume host paths passed to volumes are now treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.
• A service can now share another service's network namespace with net: container:<service>.
• volumes_from and net: container:<service> entries are taken into account when resolving dependencies, so docker-compose up <service> will correctly start all dependencies of <service>.
• docker-compose run now accepts a --user argument to specify a user to run the command as, just like docker run.
• The up, stop and restart commands now accept a --timeout (or -t) argument to specify how long to wait when attempting to gracefully stop containers, just like docker stop.
• docker-compose rm now accepts -f as a shorthand for --force, just like docker rm.

Thanks, @abesto, @albers, @alunduil, @dnephin, @funkyfuture, @gilclark, @IanVS, @KingsleyKelly, @knutwalker, @thaJeztah and @vmalloc!

1.2.0 RC4

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

curl -L https:/docker/compose/releases/download/1.2.0rc4/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Optionally, you can also install command completion for the bash shell.

On top of the changes listed below for RC1-RC3, the following bugs have been fixed:

• Environment variables and the user's home directory (~) were not expanding properly in volumes host paths.

Here are the changes for RC3:

• When copying a service's configuration with extends, image and build could come into conflict, resulting in an error, as it makes no sense to have both defined. Each now overwrites the other: if a service with image defined is extended and build is added, the image entry will be removed.
• When copying a service's configuration with extends, if both services defined a multi-value option such as ports or dns, the original value would be completely discarded. They are now concatenated instead.
• When a relative path is supplied to build, it is treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.

Here are the changes for RC2:

• A bug has been fixed where containers were being created with blank entries for "Dns" and "DnsSearch", causing DNS lookups from within a container to fail.

Here are the changes for RC1:

• docker-compose.yml now supports an extends option, which enables a service to inherit configuration from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the documentation.
• When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use build.
• Repeated invocations of docker-compose up when using Compose with a Swarm cluster now work reliably.
• Filenames in env_file and volume host paths in volumes are now treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.
• A service can now share another service's network namespace with net: container:<service>.
• volumes_from and net: container:<service> entries are taken into account when resolving dependencies, so docker-compose up <service> will correctly start all dependencies of <service>.
• Problems with authentication when using images from third-party registries have been fixed.
• docker-compose run now accepts a --user argument to specify a user to run the command as, just like docker run.
• The up, stop and restart commands now accept a --timeout (or -t) argument to specify how long to wait when attempting to gracefully stop containers, just like docker stop.
• docker-compose rm now accepts -f as a shorthand for --force, just like docker rm.

Thanks, @abesto, @albers, @alunduil, @dnephin, @funkyfuture, @gilclark, @IanVS, @KingsleyKelly, @knutwalker, @moysesb, @thaJeztah and @vmalloc!

1.2.0 RC3

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

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

Optionally, you can also install command completion for the bash shell.

On top of the changes listed below for RC1 and RC2, the following bugs have been fixed:

• When copying a service's configuration with extends, image and build could come into conflict, resulting in an error, as it makes no sense to have both defined. Each now overwrites the other: if a service with image defined is extended and build is added, the image entry will be removed.
• When copying a service's configuration with extends, if both services defined a multi-value option such as ports or dns, the original value would be completely discarded. They are now concatenated instead.
• When a relative path is supplied to build, it is treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.

Here are the changes for RC2:

• A bug has been fixed where containers were being created with blank entries for "Dns" and "DnsSearch", causing DNS lookups from within a container to fail.

Here are the changes for RC1:

• docker-compose.yml now supports an extends option, which enables a service to inherit configuration from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the documentation.
• When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use build.
• Repeated invocations of docker-compose up when using Compose with a Swarm cluster now work reliably.
• Filenames in env_file and volume host paths in volumes are now treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.
• A service can now share another service's network namespace with net: container:<service>.
• volumes_from and net: container:<service> entries are taken into account when resolving dependencies, so docker-compose up <service> will correctly start all dependencies of <service>.
• Problems with authentication when using images from third-party registries have been fixed.
• docker-compose run now accepts a --user argument to specify a user to run the command as, just like docker run.
• The up, stop and restart commands now accept a --timeout (or -t) argument to specify how long to wait when attempting to gracefully stop containers, just like docker stop.
• docker-compose rm now accepts -f as a shorthand for --force, just like docker rm.

Thanks, @abesto, @albers, @alunduil, @dnephin, @funkyfuture, @gilclark, @IanVS, @KingsleyKelly, @knutwalker, @moysesb, @thaJeztah and @vmalloc!

1.2.0 RC2

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

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

Optionally, you can also install command completion for the bash shell.

• On top of the changes listed below for RC1, a bug has been fixed where containers were being created with blank entries for "Dns" and "DnsSearch", causing DNS lookups from within a container to fail.

Here are the changes for RC1:

• docker-compose.yml now supports an extends option, which enables a service to inherit configuration from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the documentation.
• When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use build.
• Repeated invocations of docker-compose up when using Compose with a Swarm cluster now work reliably.
• Filenames in env_file and volume host paths in volumes are now treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.
• A service can now share another service's network namespace with net: container:<service>.
• volumes_from and net: container:<service> entries are taken into account when resolving dependencies, so docker-compose up <service> will correctly start all dependencies of <service>.
• Problems with authentication when using images from third-party registries have been fixed.
• docker-compose run now accepts a --user argument to specify a user to run the command as, just like docker run.
• The up, stop and restart commands now accept a --timeout (or -t) argument to specify how long to wait when attempting to gracefully stop containers, just like docker stop.
• docker-compose rm now accepts -f as a shorthand for --force, just like docker rm.

Thanks, @abesto, @albers, @alunduil, @dnephin, @funkyfuture, @gilclark, @IanVS, @KingsleyKelly, @knutwalker, @thaJeztah and @vmalloc!