-
Notifications
You must be signed in to change notification settings - Fork 36
dockerComposeTest does not clean up custom networks #55
Comments
Quick question: Why is the plugin tyring to keep track of the running instances and stopping them? It seems that the plugin is reimplementing docker-compose functionality. Is it because the containers/networks should remain afterwards? |
Hi @Tillaert, Thanks for reporting this issue! I have released a Let me know if it works for you and I'll merge it into master.
|
The current 1.0.21-SNAPSHOT indeed cleans up the networks 👍 |
Closing this issue out as there is now an official release that includes this update:
@Tillaert - Thanks again for your assistance. |
Given a docker compose file:
After running dockerComposeTest:
And
docker network ls
shows:It seems that dockerComposeTest uses
docker-compose stop
to stop the containers.docker-compose down
will clean up resources properly.The text was updated successfully, but these errors were encountered: