Check if container is created/running before stopping/removing #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems this project is no longer maintained and this PR is been chilling for a minute. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Method
Helper scripts are available to start/stop/enter containers.
Expected Behavior
When executing the
stop.shscript containers should be stop and removedActual Result
While the scripts is able stop/remove the containers called in
start.shan error appears.Cause
The
dockercommand to stop/remove containers list thedeepdream-entercontainer that may not always have been created/running.Solution
Check the status of the
deepdream-entercontainer before trying to stop/remove it.Fixes #35