docs: document engine container event sequences in up monitor - #14024
Open
ndeloof wants to merge 1 commit into
Open
docs: document engine container event sequences in up monitor#14024ndeloof wants to merge 1 commit into
ndeloof wants to merge 1 commit into
Conversation
Map, per container lifecycle scenario, the exact event sequences the engine emits and the monitor may receive: natural exit, policy-driven restart (die/start only, no restart action, silence during backoff), external stop of a running vs restarting container, ContainerRestart, docker kill, OOM kill, rm -f and rm. Mapped from moby's daemon sources (LogContainerEvent call sites and handleContainerExit/containerStop/containerRestart/kill paths) and verified against a live engine v29.6.1 with 'docker events'. Notably: the relative order of stop and die on a container stop is not guaranteed, and no event at all is emitted while a container sits in restart backoff. Related to #13985 / #13990. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
ndeloof
force-pushed
the
doc-monitor-container-events
branch
from
August 11, 2026 11:59
51a2ce7 to
1e8654a
Compare
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
1 participant
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
Documentation-only: add a comment block above
monitor.Startmapping, per container lifecycle scenario, the exact event sequences the engine emits and the monitor may receive — natural exit, policy-driven restart (die/startonly, norestartaction, complete silence during backoff), external stop of a running vs restarting container,ContainerRestart,docker kill, OOM kill,rm -f/rm.Mapped from moby's daemon sources (
LogContainerEventcall sites,handleContainerExit,containerStop/containerRestart/killpaths) and verified against a live engine v29.6.1 withdocker events. Two findings worth calling out: the relative order ofstopanddieon a container stop is not guaranteed, and a container stopped while in restart backoff emitsstoponly (the root cause of #13985).Related issue
Context for #13985 / #13990.