versions of Python 3
- Fixed a bug where the output of `docker-compose config` would sometimes
contain invalid port definitions
## 1.13.0
(2017-05-02)
### Breaking changes
- `docker-compose up` now resets a service's scaling to its default value.
You can use the newly introduced `--scale` option to specify a custom
scale value
### New features
#### Compose file version 2.2
- Introduced version 2.2 of the `docker-compose.yml` specification. This
version requires to be used with Docker Engine 1.13.0 or above
- Added support for `init` in service definitions.
- Added support for `scale` in service definitions. The configuration's value
can be overridden using the `--scale` flag in `docker-compose up`.
The `scale` command is disabled for this file format
#### Compose file version 2.x
- Added support for `options` in the `ipam` section of network definitions
### Bug fixes
- Fixed a bug where paths provided to compose via the `-f` option were not
being resolved properly
- Fixed a bug where the `ext_ip::target_port` notation in the ports section
was incorrectly marked as invalid
- Fixed an issue where the `exec` command would sometimes not return control
to the terminal when using the `-d` flag
- Fixed a bug where secrets were missing from the output of the `config`
command for v3.2 files
- Fixed an issue where `docker-compose` would hang if no internet connection
was available
- Fixed an issue where paths containing unicode characters passed via the `-f`
flag were causing Compose to crash
- Fixed an issue where the output of `docker-compose config` would be invalid
if the Compose file contained external secrets
- Fixed a bug where using `--exit-code-from` with `up` would fail if Compose
was installed in a Python 3 environment
- Fixed a bug where recreating containers using a combination of `tmpfs` and
`volumes` would result in an invalid config state
## 1.12.0
(2017-04-04)
### New features
#### Compose file version 3.2
- Introduced version 3.2 of the `docker-compose.yml` specification
- Added support for `cache_from` in the `build` section of services
- Added support for the new expanded ports syntax in service definitions
- Added support for the new expanded volumes syntax in service definitions
#### Compose file version 2.1
- Added support for `pids_limit` in service definitions
#### Compose file version 2.0 and up
- Added `--volumes` option to `docker-compose config` that lists named
volumes declared for that project
- Added support for `mem_reservation` in service definitions (2.x only)
- Added support for `dns_opt` in service definitions (2.x only)
#### All formats
- Added a new `docker-compose images` command that lists images used by
the current project's containers
- Added a `--stop` (shorthand `-s`) option to `docker-compose rm` that stops
the running containers before removing them
- Added a `--resolve-image-digests` option to `docker-compose config` that
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