[FIX] check running now check if the container is created otherwise you #162
Conversation
This file contains hidden or 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
Contributor
Author
|
@sebastienbeau bump |
1 similar comment
Contributor
Author
|
@sebastienbeau bump |
In some case (a failing execution of docker/docky run) or if you have used the docker create cmd, a docker container can be in the state created which is not a running state, so we can remove this container instead of raising an error
sebastienbeau
force-pushed
the
running-created-container
branch
from
f356c99 to
0ea3c23
Compare
Member
|
@FranzPoize thanks for your fix ! and sorry for the delay ! |
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.
can't run docky run if your container is created but not running