bugfix: sync abnormal container status when start pouchd #1056
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.
Signed-off-by: Michael Wan [email protected]
Ⅰ. Describe what this PR did
Killing a container after
pouchd
service quit, then start thepouchd
service, the killed container's status still berunning
so we must sync all abnormal containers's status when starting the
pouchd
service.pouch ps
choose a container to perform an experiment, in this case, we choose80ec87
pouchd
service quit.pouchd
service again, then the container'status should be stopped:pouch daemon logs:
Ⅱ. Does this pull request fix one issue?
fixes #898 #927
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews