You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 19, 2026. It is now read-only.
additionalimagestores is ignored even inside the same privileged container: a shared store created by Podman cannot be read by another Podman storage root in that same container #2392
podman build / buildah from --pull=never would also behave as if the image is absent
This is not a host bind mount problem, not a rootless permission problem, and not a cross-machine scenario, because the entire reproducer runs inside one privileged container.
Steps to reproduce
Run this command:
podman run --rm --privileged quay.io/podman/stable:latest sh -eux <<'EOF'
mkdir -p /work/shared/graphroot /work/shared/runroot
mkdir -p /work/consumer/graphroot /work/consumer/runroot
The producer side sees the image in the shared store:
== producer images ==
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/ubuntu latest f794f40ddfff 5 weeks ago 80.7 MB
But the consumer side sees nothing:
== consumer images ==
REPOSITORY TAG IMAGE ID CREATED SIZE
And image exists reports the image as absent:
== consumer image exists ==
exit code: 1
Expected results
I expect the consumer store to see images from the producer store listed in additionalimagestores, especially in this minimal case where both stores are created and used inside
the same privileged container.
Expected behavior:
podman images should show docker.io/library/ubuntu:latest
podman image exists docker.io/library/ubuntu:latest should return success
Why I think this belongs in containers/storage
This reproducer avoids most of the usual Podman-in-Podman complications:
same privileged container
same filesystem namespace
same runtime environment
same storage driver (overlay)
producer and consumer are both Podman
no host bind-mounted rootless store involved
Podman successfully writes and reads the producer store when used directly.
The failure only appears when a second storage root tries to consume that store through additionalimagestores.
That suggests the problem is in how containers/storage recognizes or exposes additional image stores, not in CLI behavior.
Environment
Reproducer container:
Image: quay.io/podman/stable:latest
Podman: 5.8.1
podman --version:
podman version 5.8.1
Host environment where I originally noticed the issue:
Podman: 4.9.3
Ubuntu 24.04
kernel: 6.6.87.2-microsoft-standard-WSL2
But the reproducer above does not depend on the host storage layout and happens fully inside a single privileged container.
Activity
github-actions commentedon Mar 31, 2026
This repository has been migrated to https://github.com/containers/container-libs. Please open your issue there.