Home Explore Blog CI



docker

41th chunk of `content/manuals/compose/releases/release-notes.md`
9bfa560cccaab41de35d7ab0b61cd0a69e1922474c222b840000000100000fd3
  pins the image version for each service to a permanent digest

- Added a `--exit-code-from SERVICE` option to `docker-compose up`. When
  used, `docker-compose` will exit on any container's exit with the code
  corresponding to the specified service's exit code

- Added a `--parallel` option to `docker-compose pull` that enables images
  for multiple services to be pulled simultaneously

- Added a `--build-arg` option to `docker-compose build`

- Added a `--volume <volume_mapping>` (shorthand `-v`) option to
  `docker-compose run` to declare runtime volumes to be mounted

- Added a `--project-directory PATH` option to `docker-compose` that will
  affect path resolution for the project

- When using `--abort-on-container-exit` in `docker-compose up`, the exit
  code for the container that caused the abort will be the exit code of
  the `docker-compose up` command

- Users can now configure which path separator character they want to use
  to separate the `COMPOSE_FILE` environment value using the
  `COMPOSE_PATH_SEPARATOR` environment variable

- Added support for port range to a single port in port mappings, such as
  `8000-8010:80`.

### Bug fixes

- `docker-compose run --rm` now removes anonymous volumes after execution,
  matching the behavior of `docker run --rm`.

- Fixed a bug where override files containing port lists would cause a
  TypeError to be raised

- Fixed a bug where the `deploy` key would be missing from the output of
  `docker-compose config`

- Fixed a bug where scaling services up or down would sometimes re-use
  obsolete containers

- Fixed a bug where the output of `docker-compose config` would be invalid
  if the project declared anonymous volumes

- Variable interpolation now properly occurs in the `secrets` section of
  the Compose file

- The `secrets` section now properly appears in the output of
  `docker-compose config`

- Fixed a bug where changes to some networks properties would not be
  detected against previously created networks

- Fixed a bug where `docker-compose` would crash when trying to write into
  a closed pipe

- Fixed an issue where Compose would not pick up on the value of
  COMPOSE_TLS_VERSION when used in combination with command-line TLS flags

## 1.11.2

(2017-02-17)

### Bug fixes

- Fixed a bug that was preventing secrets configuration from being
  loaded properly

- Fixed a bug where the `docker-compose config` command would fail
  if the config file contained secrets definitions

- Fixed an issue where Compose on some linux distributions would
  pick up and load an outdated version of the requests library

- Fixed an issue where socket-type files inside a build folder
  would cause `docker-compose` to crash when trying to build that
  service

- Fixed an issue where recursive wildcard patterns `**` were not being
  recognized in `.dockerignore` files.

## 1.11.1

(2017-02-09)

### Bug fixes

- Fixed a bug where the 3.1 file format was not being recognized as valid
  by the Compose parser

## 1.11.0

(2017-02-08)

### New Features

#### Compose file version 3.1

- Introduced version 3.1 of the `docker-compose.yml` specification. This
  version requires Docker Engine 1.13.0 or above. It introduces support
  for secrets. See the documentation for more information

#### Compose file version 2.0 and up

- Introduced the `docker-compose top` command that displays processes running
  for the different services managed by Compose.

### Bug fixes

- Fixed a bug where extending a service defining a healthcheck dictionary
  would cause `docker-compose` to error out.

- Fixed an issue where the `pid` entry in a service definition was being
  ignored when using multiple Compose files.

## 1.10.1

(2017-02-01)

### Bug fixes

- Fixed an issue where the presence of older versions of the docker-py
  package would cause unexpected crashes while running Compose

- Fixed an issue where healthcheck dependencies would be lost when
  using multiple compose files for a project

- Fixed a few issues that made the output of the `config` command

Title: Docker Compose Versions 1.11.0-1.12.0: Bug Fixes and Feature Additions
Summary
Docker Compose versions 1.11.0 through 1.12.0 introduce new features and bug fixes. Version 1.12.0 adds options like `--resolve-image-digests`, `--exit-code-from`, `--parallel`, `--build-arg`, `--volume`, and `--project-directory`. It also allows configuring `COMPOSE_PATH_SEPARATOR` and supports port ranges. Bug fixes address issues with `docker-compose run --rm`, port lists, missing `deploy` key in `config`, scaling services, anonymous volumes, secrets interpolation, network changes, closed pipe errors, and `COMPOSE_TLS_VERSION`. Version 1.11.2 fixes secrets, `config` with secrets, outdated `requests`, socket files, and `.dockerignore` patterns. Version 1.11.1 fixes the 3.1 file format. Version 1.11.0 introduces Compose file 3.1 (secrets) and `docker-compose top`, and fixes healthcheck and `pid` issues. Version 1.10.1 addresses crashes due to older `docker-py`, healthcheck dependencies, and `config` command issues.