Repository navigation
Ignore podman-docker shim during session discovery - #261
Merged
Merged
Conversation
When /usr/bin/docker is the podman-docker shim, paude probed both the podman and docker engines and found every session twice. The registry merge let the docker copy win, so `paude list` reported podman sessions under the docker backend, name-less commands could see "multiple sessions", and workflows paired sessions with a Docker-flavored backend. Add ContainerEngine.is_podman_shim (a cached `docker --version` probe) and a shared real_docker_backend() helper that returns None for a shim. Session discovery and find_session_backend use it to skip docker, and collect_all_sessions dedupes by name in one pass (podman first) as a safety net for other aliasing setups. Explicit --backend=docker on a shim host still uses Docker-flavored flags; tracked as ENGINE-001 in KNOWN_ISSUES.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When /usr/bin/docker is the podman-docker shim, paude probed both the podman and docker engines and found every session twice. The registry merge let the docker copy win, so
paude listreported podman sessions under the docker backend, name-less commands could see "multiple sessions", and workflows paired sessions with a Docker-flavored backend.Add ContainerEngine.is_podman_shim (a cached
docker --versionprobe) and a shared real_docker_backend() helper that returns None for a shim. Session discovery and find_session_backend use it to skip docker, and collect_all_sessions dedupes by name in one pass (podman first) as a safety net for other aliasing setups.Explicit --backend=docker on a shim host still uses Docker-flavored flags; tracked as ENGINE-001 in KNOWN_ISSUES.md.