- Added new `--no-start` to the `up` command, allowing users to create all
resources (networks, volumes, containers) without starting services.
The `create` command is deprecated in favor of this new option
### Bug fixes
- Fixed a bug where `extra_hosts` values would be overridden by extension
files instead of merging together
- Fixed a bug where the validation for v3.2 files would prevent using the
`consistency` field in service volume definitions
- Fixed a bug that would cause a crash when configuration fields expecting
unique items would contain duplicates
- Fixed a bug where mount overrides with a different mode would create a
duplicate entry instead of overriding the original entry
- Fixed a bug where build labels declared as a list wouldn't be properly
parsed
- Fixed a bug where the output of `docker-compose config` would be invalid
for some versions if the file contained custom-named external volumes
- Improved error handling when issuing a build command on Windows using an
unsupported file version
- Fixed an issue where networks with identical names would sometimes be
created when running `up` commands concurrently.
## 1.16.0
(2017-08-31)
### New features
#### Compose file version 2.3
- Introduced version 2.3 of the `docker-compose.yml` specification.
This version requires to be used with Docker Engine 17.06.0 or above.
- Added support for the `target` parameter in build configurations
- Added support for the `start_period` parameter in healthcheck
configurations
#### Compose file version 2.x
- Added support for the `blkio_config` parameter in service definitions
- Added support for setting a custom name in volume definitions using
the `name` parameter (not available for version 2.0)
#### All formats
- Added new CLI flag `--no-ansi` to suppress ANSI control characters in
output
### Bug fixes
- Fixed a bug where nested `extends` instructions weren't resolved
properly, causing "file not found" errors
- Fixed several issues with `.dockerignore` parsing
- Fixed issues where logs of TTY-enabled services were being printed
incorrectly and causing `MemoryError` exceptions
- Fixed a bug where printing application logs would sometimes be interrupted
by a `UnicodeEncodeError` exception on Python 3
- The `$` character in the output of `docker-compose config` is now
properly escaped
- Fixed a bug where running `docker-compose top` would sometimes fail
with an uncaught exception
- Fixed a bug where `docker-compose pull` with the `--parallel` flag
would return a `0` exit code when failing
- Fixed an issue where keys in `deploy.resources` were not being validated
- Fixed an issue where the `logging` options in the output of
`docker-compose config` would be set to `null`, an invalid value
- Fixed the output of the `docker-compose images` command when an image
would come from a private repository using an explicit port number
- Fixed the output of `docker-compose config` when a port definition used
`0` as the value for the published port
## 1.15.0
(2017-07-26)
### New features
#### Compose file version 2.2
- Added support for the `network` parameter in build configurations.
#### Compose file version 2.1 and up
- The `pid` option in a service's definition now supports a `service:<name>`
value.
- Added support for the `storage_opt` parameter in service definitions.
This option is not available for the v3 format
#### All formats
- Added `--quiet` flag to `docker-compose pull`, suppressing progress output
- Some improvements to CLI output
### Bug fixes
- Volumes specified through the `--volume` flag of `docker-compose run` now
complement volumes declared in the service's definition 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 `credHelpers` entries in the `config.json` file
were not being honored by Compose
- Fixed a bug where using multiple Compose files with port declarations