Docker persistent sandbox recovery from external container removal
Cluster 36266. Data as of
Nothing open on GitHub. Fix merged in #39415 on 5 Jun 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 #39415. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #39415. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the gateway loops indefinitely on 'No such container' when a pinned container is removed outside of the sandbox's control, plus associated fix attempts. The cluster covers the problem report and two related fix pull requests addressing recovery/re-spawning behavior in persistent mode.
Open issues0
Open PRs0
Fixes on record
-
#39415 fix(docker): recover from out-of-band container removal in persistent mode (salvage #36631)
files:
tests/tools/test_docker_environment.py,tools/environments/docker.py
1 PR closed without merging
From the close comments: closed without comment 1
- #36631 fix(docker): recover from out-of-band container removal in persistent mode · closed without comment
Closed issues · 1
- Closed#36266Persistent docker sandbox: gateway loops on `No such container` when the pinned container is removed out-of-band (never re-spawns)
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
- #39415
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 5 Jun 2026