DockerComposeEnvironment is missing getServicePort

[nidomiro]

The java version of DockerComposeEnvironment supports getServicePort, which can be used to retrieve dynamic port mappings.

In my usecase I want to start a Compose file with randomized exposed ports for test isolation, but the application under test should still be able to communicate with the services.

A workaround is to use this:

const pgContainer = startedComposeEnv.getContainer('postgres-1');
const pgPort = pgContainer.getMappedPort('5432/tcp')

Is the workaround I presented really a workaround, or did you explicitly decide not to do it the java way?

[cristianrgreco]

It's not a workaround, it's intentional. There's no need to duplicate the entire Testcontainer interface in the DockerComposeEnvironment, so as you found you can get the container from the environment and do everything that you can do with a regular container

[nidomiro]

Can we then maybe improve the documentation?

[cristianrgreco]

https://node.testcontainers.org/features/compose/#interacting-with-the-containers