-
Notifications
You must be signed in to change notification settings - Fork 645
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 killing and removing all spawned containers #1182
Comments
Not sure if I understand you correctly when you say 'kill on every' container, and why this is faster than proper docker:stop. |
I think he means that a regular docker stop would wait for the process to terminate correctly while a hard docker rm -f would terminate the process with a sigkill which is faster for some heavy application servers. |
I see and think it might be a valid use case for testing. I'm positive for adding a However, I can't do the coding but would happy to support a submitted PR (if you have some patience, as I'm really low on time which I can spend on d-m-p) |
@rhuss : Shall I look into this? |
@rohanKanojia would be awesome. You are the best ;-) |
We use the maven plugin for integration testing. The stopping of every container in a sequential order takes some time. As it is used just for testing, it would be better if the plugin could offer a mechanism to execute docker kill on every container, which should be almost immediate.
The text was updated successfully, but these errors were encountered: