Orphan reaper unsafe force-removal of live containers
Cluster 115697. Data as of
Nothing open on GitHub. Fix merged in #116723 on 20 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 #116723. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116723. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a race condition where the orphan reaper's forced container removal could kill a container that a sibling process had just restarted. The proposed fix removes the force flag so running containers are left untouched.
Open issues0
Open PRs0
Fixes on record
-
#116723 fix(docker): the orphan reaper no longer force-removes a container a sibling just restarted (#115697, salvage #115699)
files:
tests/tools/test_docker_environment.py,tools/environments/docker.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#115699 fix(docker): drop -f from orphan reaper rm so running containers fail safe · merged via another change →
e885d9c,#116723,#115697,#115699
Closed issues · 1
- Closed#115697Orphan reaper's docker rm -f can kill a sibling's live container (exited-snapshot TOCTOU)
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
- Merged PRs
- #116723
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026