DockerComposeContainer not working for version 2 of compose format

[jlordiales]

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

[rnorth]

I think this is going to necessitate an upgrade to v3 of the docker-java library to benefit from docker-java/docker-java#425.

[rnorth]

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]

Sounds awesome! Looking forward to it

[rnorth]

v2 networks should be working properly now in the branch for #156