-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman run --override-arch do not download the image with correct architecture if the image with other architecture is exists. #8001
Comments
I take it you meant to say
|
@vrothberg PTAL |
@rhatdan, I can tackle the bug once short names are merged. Thanks for opening the issue, @lisongmin |
When pulling an image, account for the specified OS, architecture and variant when looking up local images. While a local image may be found based on the specified name, the platform may be different from what the user desires. In that case, do not use the local image but continue pulling. Also remove pull-policy logic from the client. That'll reduce one roundtrip for the remote client and reduces code scattering. The backend should be the single source of truth for pull-policy handling. Fixes: containers#8001 Signed-off-by: Valentin Rothberg <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
@vrothberg Reminder. Shortnames has merged. :^) |
Maybe I am a dreamer :) Right after short names, |
This is now working for me on Buildah, although I am dropping --override-arch and just using --arch. |
A friendly reminder that this issue had no activity for 30 days. |
Currently podman implements --override-arch and --overide-os But Podman has made these aliases for --arch and --os. No reason to have to specify --override, since it is clear what the user intends. Currently if the user specifies an --override-arch field but the image was previously pulled for a different Arch, podman run uses the different arch. This PR also fixes this issue. Fixes: containers#8001 Signed-off-by: Daniel J Walsh <[email protected]>
Currently podman implements --override-arch and --overide-os But Podman has made these aliases for --arch and --os. No reason to have to specify --override, since it is clear what the user intends. Currently if the user specifies an --override-arch field but the image was previously pulled for a different Arch, podman run uses the different arch. This PR also fixes this issue. Fixes: containers#8001 Signed-off-by: Daniel J Walsh <[email protected]>
Currently podman implements --override-arch and --overide-os But Podman has made these aliases for --arch and --os. No reason to have to specify --override, since it is clear what the user intends. Currently if the user specifies an --override-arch field but the image was previously pulled for a different Arch, podman run uses the different arch. This PR also fixes this issue. Fixes: containers#8001 Signed-off-by: Daniel J Walsh <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
docker run --override-arch
do not download the image with correct architecture if the image with other architecture is exists.Steps to reproduce the issue:
--override-arch=arm64
. The arch is x86_64, which is unexpectedDescribe the results you received:
podman do not try to download image with correspoding architecture if image with another arch is exists.
Describe the results you expected:
podman should try to download the image if architecture is not matching.
It may be a good idea that podman can cache same tag with diff arch,
so we do not need to download image again and again when we run multiple architecture containers on the same node.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: