- Fixed error on duplicate mount points (a configuration error message now displays).
- Fixed the merge on `networks` section.
- Compose container is always connected to `stdin` by default.
- Fixed the presentation of failed services on the `docker-compose start` command when containers are not available.
## 1.24.1
(2019-06-24)
This release contains minor improvements and bug fixes.
## 1.24.0
(2019-03-28)
### Features
- Added support for connecting to the Docker Engine using the `ssh` protocol.
- Added an `--all` flag to `docker-compose ps` to include stopped one-off containers
in the command's output.
- Added bash completion for `ps --all|-a`.
- Added support for credential_spec.
- Added `--parallel` to `docker build`'s options in `bash` and `zsh` completion.
### Bug fixes
- Fixed a bug where some valid credential helpers weren't properly handled by Compose
when attempting to pull images from private registries.
- Fixed an issue where the output of `docker-compose start` before containers were created
was misleading.
- Compose will no longer accept whitespace in variable names sourced from environment files.
This matches the Docker CLI behavior.
- Compose will now report a configuration error if a service attempts to declare
duplicate mount points in the volumes section.
- Fixed an issue with the containerized version of Compose that prevented users from
writing to stdin during interactive sessions started by `run` or `exec`.
- One-off containers started by `run` no longer adopt the restart policy of the service,
and are instead set to never restart.
- Fixed an issue that caused some container events to not appear in the output of
the `docker-compose events` command.
- Missing images will no longer stop the execution of `docker-compose down` commands. A warning is
now displayed instead.
- Force `virtualenv` version for macOS CI.
- Fixed merging of Compose files when network has `None` config.
- Fixed `CTRL+C` issues by enabling `bootloader_ignore_signals` in `pyinstaller`.
- Bumped `docker-py` version to `3.7.2` to fix SSH and proxy configuration issues.
- Fixed release script and some typos on release documentation.
## 1.23.2
(2018-11-28)
### Bug fixes
- Reverted a 1.23.0 change that appended random strings to container names
created by `docker-compose up`, causing addressability issues.
> [!NOTE]
>
> Containers created by `docker-compose run` will continue to use randomly generated names to avoid collisions during parallel runs.
- Fixed an issue where some `dockerfile` paths would fail unexpectedly when
attempting to build on Windows.
- Fixed a bug where build context URLs would fail to build on Windows.
- Fixed a bug that caused `run` and `exec` commands to fail for some otherwise
accepted values of the `--host` parameter.
- Fixed an issue where overrides for the `storage_opt` and `isolation` keys in
service definitions weren't properly applied.
- Fixed a bug where some invalid Compose files would raise an uncaught
exception during validation.
## 1.23.1
(2018-11-01)
### Bug fixes
- Fixed a bug where working with containers created with a version of Compose earlier than `1.23.0`
would cause unexpected crashes.
- Fixed an issue where the behavior of the `--project-directory` flag would
vary depending on which subcommand was used.
## 1.23.0
(2018-10-30)
### Important note
The default naming scheme for containers created by Compose in this version
has changed from `<project>_<service>_<index>` to
`<project>_<service>_<index>_<slug>`, where `<slug>` is a randomly-generated
hexadecimal string. Please make sure to update scripts relying on the old
naming scheme accordingly before upgrading.
### Features
- Logs for containers restarting after a crash will now appear in the output
of the `up` and `logs` commands.
- Added `--hash` option to the `docker-compose config` command, allowing users
to print a hash string for each service's configuration to facilitate rolling