About exposed ports in docker-compose, when used in tests

[tarilabs]

Hi,
in our team we use TestContainers for integration test of several docker-compose.yml files. Generally, it works fine. However we have some limitations in CI context, given only one integration-test suite can run at a given time, as the docker compose file indeed exposes the ports.

I understand, as written in the TestContainers docs, the solution could be technically from the TestContainers perspective to elide/remove the ports from the docker compose file.

However, the same docker-compose.yml is used by end-users for their examples and testing, so it's nice the ports are bound in the yaml file, that is a requirement, so the end user can make use of the project's docker compose file to play and experiment with the example/software/tutorial.

So it's a short-blanket problem:

• on one hand, we really want the docker-compose.yml to expose the ports, to serve our end-users
• on other hand, we would like to integration-test the docker-compose files using TestContainers, but we would like TestContainers to ignore the ports from the yaml so we can parallelize the integration test suites.

👉 I was wondering if others have faced the same limitation.

👉 I was wondering if TestContainers could consider having a configuration option to ignore the ports from the docker compose passed as parameter to the TestContainers API.

Thank you in advance 🙏