-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow DockerComposeModule to start only certain services #1497
Comments
I already did some changes in my fork. |
Thank you - this sounds like an excellent proposal. This actually makes a major improvement for one of my previous personal use cases for this, where I put services in separate docker compose files to enable this kind of split. Your proposal is much better - thanks! |
We're trying to convert over to using the DockerComposeModule and since we're on docker-compose v3 we can't use the |
This was released in 1.11.4 🎉 |
It's important to mention that I had to use an old version. Details: - testcontainers/testcontainers-java#1010 - testcontainers/testcontainers-java#1497
Hi everyone,
Actually I am using the DockerComposeContainer of Testcontainers for CDCTs of my services. For the provider verification it is necessary to start up the services, and that is the part, where Testcontainers helps me out.
Actually, my compose file comprises out of 22 services and 500 lines and I only want to start one of these services. So the enhancement of just starting up certain containers would be a really nice approach to me.
I really would like to see this feature and I will keep following the development of this framework. Thanks to the team of Testcontainers and keep going on like that you helped me a lot!
The text was updated successfully, but these errors were encountered: