Podman compatibility fix for container reuse probe
Cluster 99213. Data as of
Nothing open on GitHub. Fix merged in #103645 on 5 Sep 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 #103645. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #103645. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the cross-process container reuse probe uses a Docker-only {{.Label}} template format that fails silently on Podman. The work involves making the probe compatible with Podman's podman ps behavior.
Open issues0
Open PRs0
Fixes on record
-
#103645 fix(docker): persistent container reuse works on Podman — the reuse probe no longer uses the Docker-only {{.Label}} template (#99213, salvage #99238)
files:
tests/tools/test_docker_environment.py,tools/environments/docker.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · stale or abandoned 1
Closed issues · 1
- Closed#99213[Bug]: Podman backend silently loses cross-process container reuse — egress=off reuse probe uses Docker-only {{.Label "..."}} format, podman ps exits 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.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 LabAt a glance
- Merged PRs
- #103645
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 5 Sep 2026