victor
December 6, 2018, 11:54pm
21
@Fadi
as per @pmp ’s fix above, can you please upgrade your docker-compose version from 1.23.1 to 1.23.2 ? For reference, see: https://docs.docker.com/compose/install/
As per docker-compose change log, they introduced a naming bug in 1.23.0 that persisted in 1.23.1 (your version from the network screenshot above) and they fixed it on 1.23.2. For reference, see:
Change log
==========
1.23.2 (2018-11-28)
-------------------
### Bugfixes
- 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.
show original