-
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 tries update container on every start after adding "--platform=linux/amd64" key to "podman run" command. #16425
Comments
Thanks for reaching out, @NTMan! By "updating" I assume you refer to "pulling" down the image? |
yes |
A friendly reminder that this issue had no activity for 30 days. |
I am only seeing this when I switch back and forth between two images. If I run the same container twice, it only pulls once.
If I change arches it pulls again.
Then if I switch back to the original arch, it pulls again.
|
A friendly reminder that this issue had no activity for 30 days. |
This is the same issue as #17063 which has been fixed. The upcoming Podman 4.4 release will ship the fix. |
I am again faced to this bug with podman 4.5.0 |
Please follow the linked issue above. As mentioned in #17063 (comment), we had to revert the fix as it caused regressions on other sides. Apologies, I know it's not an ideal behavior for this use case but it's tough to iron it out. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
To unify the startup script, I added the "--platform=linux/amd64" key to the "podman run" command to support running containers on MacOs.
But it leads to update container on every start.
Steps to reproduce the issue:
Describe the results you received:
On every launch podman tries update container.
Describe the results you expected:
I update container when I want. (podman didn't tries update container automatically on every launch)
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):The text was updated successfully, but these errors were encountered: