Docker sandbox mount fails due to colons in session IDs
Cluster 92640. Data as of
Nothing open on GitHub. Fix merged in #93488 on 24 Aug 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 #93488. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93488. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Session task IDs containing colons (e.g. 'session:{key}') cause Docker volume mount parsing to fail with exit 125. These issues and PRs address stripping colons from session IDs before they are used as sandbox directory paths.
Open issues0
Open PRs0
Fixes on record
-
#93488 Colon-bearing session ids no longer break sandbox mounts (#92414, consolidates 6 PRs)
files:
tests/tools/test_base_environment.py,tests/tools/test_docker_environment.py,tests/tools/test_singularity_persistent_overlay.py,tools/environments/base.py,tools/environments/docker.py,tools/environments/singularity.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#92646 fix(docker): strip colons from session task_id before it becomes a sandbox path (#92640) · superseded by another PR →
ec44116,#93488,#92331
Closed issues · 1
- Closed#92640Docker backend: per-session sandbox dir contains colons (session:{key}) → -v mount parse fails with exit 125
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
- #93488
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Aug 2026