First off, you should not need to pass any special flags like --arch.
This part is automatic unless you intentionally want to run another arch
via emulation. If so, you need Rosetta enabled, and the form should be
"--arch amd64" (drop the "linux/" part).
Note: I'm assuming your podman-machine is running the arm64 VM iamge
(again, this should be automatic).
What is also possibly happening is the image itself may not be built for
ARM64. Unfortunately the repo. seems to require auth, so I cannot check
it for you. You can verify what architectures are supported with the
command (from inside the podman-machine vm, unless you have a native
copy of skopeo):
skopeo inspect --raw \
docker://ghcr.io/code-with-mehdi/rabbitmq:3-management \
| jq -re '.manifests[].platform.architecture'
If that gives you a "jq" error, or no "arm64" in the output, then
it's
probably not a image manifest-list and/or not built for arm64.
Hope that helps.
---
Chris Evich (he/him)
Senior Quality Assurance Engineer
If there's a "hard-way", I'm the first one to implement it.
On 6/12/24 09:39, Mehdi Haghgoo via Podman wrote:
Hi all,
I'm trying to run rabbitmq images on MacBook M1 and I see warnings like:
WARNING: image platform (linux/amd64) does not match the expected platform
(linux/linux/arm64)
I run the command:
podman run --rm -p 8000:8080 --arch linux/arm64
ghcr.io/code-with-mehdi/rabbitmq:3-management
and it fails to boot with a lot of logs that I like below:
Mozilla Community Pastebin/QTExU80S (Plain Text)
Mozilla Community Pastebin/QTExU80S (Plain Text)
Is there a special flag I need to pass to fetch arm64 images?
I'm not sure the boot issue has anything to do with the image arch incompatibility,
though. Some enlightening on this from someone who has experience and insight will be
appreciated.
Best regards,
Mehdi
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io