Closed twardnw closed 3 years ago
Prioritizing this one - but similar was noted in #271
Some questions about expected behavior:
The current behavior in the gem version is to stop the containers (but not remove) and clean up the resolver. The network stays in place for stop
There's now a test case which replicates the behavior in #271. Once the issue is fixed and the test case passes this will be good for merging.
Currently the only option to stop the containers is with the
down
command, which removes _everything_related to Pygmy. While this is nice for cleanup, it is excessive. The Pygmy gem utilizes astop
command, which simply stops the containers. This command should be added to retain parity with the gem.