Skip to content

1.7.1
Compare
Choose a tag to compare
@shin- shin- released this 04 May 22:23
1.7.1
6c29830

Note that Compose 1.7.1 requires Docker Engine 1.10.0 or later for version 2 of the Compose File format, and Docker Engine 1.9.1 or later for version 1.

If you're a Mac or Windows user, the Docker Toolbox will install Compose 1.7.1 for you, alongside the latest versions of Docker Engine, Machine and Kitematic.

Alternatively, you can use the usual commands to install or upgrade:

curl -L https://github.com/docker/compose/releases/download/1.7.1/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.

Here's what's new:

Bug Fixes

  • Fixed a bug where the output of docker-compose config for v1 files
    would be an invalid configuration file.
  • Fixed a bug where docker-compose config would not check the validity
    of links.
  • Fixed an issue where docker-compose help would not output a list of
    available commands and generic options as expected.
  • Fixed an issue where filtering by service when using docker-compose logs
    would not apply for newly created services.
  • Fixed a bug where unchanged services would sometimes be recreated in
    in the up phase when using Compose with Python 3.
  • Fixed an issue where API errors encountered during the up phase would
    not be recognized as a failure state by Compose.
  • Fixed a bug where Compose would raise a NameError because of an undefined
    exception name on non-Windows platforms.
  • Fixed a bug where the wrong version of docker-py would sometimes be
    installed alongside Compose.
  • Fixed a bug where the host value output by docker-machine config default
    would not be recognized as valid options by the docker-compose
    command line.
  • Fixed an issue where Compose would sometimes exit unexpectedly while
    reading events broadcasted by a Swarm cluster.
  • Corrected a statement in the docs about the location of the .env file,
    which is indeed read from the current directory, instead of in the same
    location as the Compose file.

Thanks @aanand, @shin-, @dnephin, @bfirsh, @johnharris85, @Werehuman, @twitherspoon, @metal3d, @aronahl, @andrerom

Assets 6
Loading