Docker cold-start exec-read failure and retry fix
Cluster 76566. Data as of
Nothing open on GitHub. Fix merged in #81202 on 8 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #81202. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #81202. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where vision analysis fails on the first attempt under the Docker backend due to a sandbox read error, and a fix that adds retry logic for container exec-read during Docker cold-start while also surfacing stderr.
Open issues0
Open PRs0
Fixes on record
-
#80801 fix(tools): lazily bring up sandbox for vision_analyze reads (#62825)
files:
tests/tools/test_ensure_task_env.py,tests/tools/test_image_source.py,tools/image_source.py,tools/terminal_tool.py -
#81202 fix(vision): retry container exec-read for Docker cold-start, surface stderr (#76566)
files:
tests/tools/test_image_source.py,tools/image_source.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#76688 fix(vision): retry container exec-read for Docker cold-start, surface stderr (#76566) · merged via another change →
f46636b,#81202,#80801
Closed issues · 1
- Closed#76566vision_analyze: first attempt fails 'could not read … inside the sandbox' under Docker backend, succeeds on retry
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.50: 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 Lab