Repository navigation
DockerComposeContainer not working for version 2 of compose format #146
Description
Hi,
The DockerComposeContainer functionality seems to be broken if you are using the version 2 format of docker-compose where a new default network is created for each app.
The failing point seems to be the ambassador container, which fails to start with: "Error response from daemon: Cannot link to /5gcpep_api_1, as it does not belong to the default network".
Sample compose file:
version: '2'
services:
db:
image: postgres
environment:
POSTGRES_PASSWORD: test
POSTGRES_USER: test
api:
build: .
depends_on:
- db
Activity
[WIP] docker compose refactoring, to support scaling, better output l…
rnorth commentedon May 21, 2016
I think this is going to necessitate an upgrade to v3 of the docker-java library to benefit from docker-java/docker-java#425.
[WIP] docker compose refactoring, to support scaling, better output l…
[WIP] docker compose refactoring, to support scaling, better output l…
rnorth commentedon Jun 5, 2016
Branch refactoring work continues on this - the issue with compose v2 networks remains unfortunately. I believe the necessary network API support went into docker-java in the last few days, so I hope it will appear in RC6 of that library.
jlordiales commentedon Jun 5, 2016
Sounds awesome! Looking forward to it
[WIP] docker compose refactoring, to support scaling, better output l…
rnorth commentedon Jun 11, 2016
v2 networks should be working properly now in the branch for #156
Add extra debugging logs to help diagnose any future docker daemon co…
Add extra debugging logs to help diagnose any future docker daemon co…