Add support for `--profiles` to `DockerComposeContainer`

[jstanik]

When starting DockerComposeContainer (local) with option --profile then this option is not used when down is executed at the end of the test. As a result it does not stop container that was started as a result of using a profile. The down then fails with the error:

org.testcontainers.containers.ContainerLaunchException: Local Docker Compose exited abnormally with code 1 whilst running command: down -v
	at org.testcontainers.containers.LocalDockerCompose.invoke(DockerComposeContainer.java:773)
	at org.testcontainers.containers.DockerComposeContainer.runWithCompose(DockerComposeContainer.java:309)

In my case the true error is probably:

failed to remove network 919...72e: Error response from daemon: error while removing network: network docker-compose_default id 919...72e has active endpoints

[bjconlan]

Does the java implementation of test containers support docker-compose profiles? (from the api it isn't obvious). I noticed that the node impl supports profiles though.

https://github.com/testcontainers/testcontainers-node/releases/tag/v7.23.0

[kiview]

Testcontainers' DockerComposeContainer implementation currently does not support --profiles explicitly. As @jstanik observed, you can run the container with certain options withOptions("--profiles foo"), but as it is the case with the down command, it might not work as expected.

[eddumelendez]

Hi, I was not able to reproduce the issue but #9040 is making sure the options are passed to the down command as well. If there is a project that could easily reproduce the issue I can dig deeper.