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
When running a multi-platform image without explicitly specifying a platform, a locally cached version will be used even if it isn't the default platform.
Steps to reproduce the issue
On my amd64 host system, if I run debian:11-slim without specifying the platform, I get the amd64 image as expected:
$ podman run -it debian:11-slim apt --help | head -n1
apt 2.2.4 (amd64)
If I explicitly ask for 386, I get that, as expected:
$ podman run --platform=linux/386 -it debian:11-slim apt --help | head -n1
Resolved "debian" as an alias (/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:11-slim...
Getting image source signatures
Copying blob 71e749b27156 skipped: already exists
Copying config b5e76b3dd2 done
Writing manifest to image destination
Storing signatures
apt 2.2.4 (i386)
Surprisingly, if I run again without explicitly specifying the platform, I now get the cached 386 image:
$ podman run -it debian:11-slim apt --help | head -n1
apt 2.2.4 (i386)
This is confusing, especially in situations where a cache may be shared across multiple users.
Describe the results you received
The image of the last-requested-platform is run.
Describe the results you expected
The image corresponding to the default/host platform is run, pulling if necessary, even if the cache contains an image of a different platform.
This is normal, since Docker forgot to include "arch" from the beginning but added it afterwards in the "manifest lists" (multi-arch)... As a workaround, you can either delete the old image or use the arch-specific images in your builds.
Issue Description
When running a multi-platform image without explicitly specifying a platform, a locally cached version will be used even if it isn't the default platform.
Steps to reproduce the issue
On my amd64 host system, if I run debian:11-slim without specifying the platform, I get the amd64 image as expected:
If I explicitly ask for 386, I get that, as expected:
Surprisingly, if I run again without explicitly specifying the platform, I now get the cached 386 image:
This is confusing, especially in situations where a cache may be shared across multiple users.
Describe the results you received
The image of the last-requested-platform is run.
Describe the results you expected
The image corresponding to the default/host platform is run, pulling if necessary, even if the cache contains an image of a different platform.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: