Docker container cleanup timing and lifecycle issues
Cluster 86317 · environments. Data as of
Nothing open on GitHub. Fix merged in #103728 on 5 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #103728. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #103728. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a race condition in Docker where per-process cleanup threads may exit after stopping but before removing containers, and where detached containers may be incorrectly removed at exit rather than left behind.
Open issues0
Open PRs0
Fixes on record
-
#103728 docker: reaper-detached containers are removed at exit instead of left behind (#86317, salvage #86344)
files:
tests/tools/test_docker_teardown_drain.py,tools/environments/docker.py,tools/terminal_tool.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#86344 fix(docker): retain container-teardown threads across registry detachment (#86317) · done elsewhere →
84b70e4,#86317
Closed issues · 1
- Closed#86317Docker per-process cleanup can exit after stop but before rm, leaving stopped containers
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- environments
- Merged PRs
- #103728
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 5 Sep 2026