Handle destroy events in up monitor - #13988
Open
ousamabenyounes wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ben Younes <2910651+ousamabenyounes@users.noreply.github.com>
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
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.
What I did
Handle container
destroyevents in the attachedupmonitor sodocker compose upcan finish when an externally stopped project removes a container that never emitted adieevent.The monitor still uses
diefor exit status and restart detection;destroyonly removes the container from the tracked set so the monitor can terminate when the project is gone.Related issue
Fixes #13985
Test verification (RED -> GREEN)
RED on
origin/mainwith the new regression test only:GREEN on this branch:
Full local validation: