Add missing function `WithDockerCompose`

Is your feature request related to a problem? Please describe. I love the approach of having a single container scenario for a test case but there are also scenarios where I’d like to spin up a whole set of containers and therefore use docker-compose as declaration.

Describe the solution you’d like I’d like to spin up a set of containers by specifying a docker-compose.yml similar to the Java version https://www.testcontainers.org/modules/docker_compose/

Describe alternatives you’ve considered Not sure If there is one

• configuring the things as in the compose in code seems odd to me and leads to duplication of configuration and most of the times docker-compose.yml will also be used to deploy the application under test this would be strange.

Additional context Also other library authors could benefit from such an approach, I happen to know that https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks is using compose and I think it would be great improvement on there development experience (since you don’ t have to remember starting the containers in advance 😉 )

Cheers & let me know what you think of the idea

[LoremFooBar]

Thinking about the API design for this, I have a few points to raise:

1. Since all of the public API surface revolves around working with a single container, I propose this API for compose:

   var compose = new DockerComposeBuilder()
     .WithComposeFile("path/to/docker-compose.yml")
     .Build();
   
   await compose.UpAsync();
   await compose.DownAsync();
   

2. Regarding implementation - since compose is not part of the Docker Engine API, and the docker compose command has been part of Docker Desktop for a while now, I assume it is acceptable to use the docker compose command for the different compose methods (docker compose up, docker compose down etc.).

[HofmeisterAn]

It would be nice to consider the testcontainers-java implementation. I’m not very familiar with it, but I think it is a good idea not to differentiate too much. OC, it should still be idiomatic with .NET.