Replies: 4 comments 5 replies
-
You have to install |
Beta Was this translation helpful? Give feedback.
-
Thank you, however this is not the issue, as I had already done this:
I am able to run ppc64le containers as well for instance, just not arm32. |
Beta Was this translation helpful? Give feedback.
-
Should I create a second issue for this, or should we continue solving the bug here? |
Beta Was this translation helpful? Give feedback.
-
This happens because M1 does not have native support for arm32, which is generally expected by Linux. The issue can be avoided using the following command once after each reboot: echo ":qemu-arm:M:0:\x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-arm-static:F" > /proc/sys/fs/binfmt_misc/register For more context, see the following links: |
Beta Was this translation helpful? Give feedback.
-
Issue Description
When running the following command on an aarch64 host (an Apple M1 MBP running Fedora38 in UTM/qemu), I expect it to realize that arm32 binaries cannot be executed natively, and to use qemu-user-static like it successfully does for amd64 and others.
This is not the case, and the container fails to start with an
exec format error
.Steps to reproduce the issue
Describe the results you received
Describe the results you expected
an alpine ash prompt
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
podman 4.6.0 was installed from fedora's
updates-testing
repoAdditional information
is there something I can do to force the use of
qemu-arm-static
to run the container?Beta Was this translation helpful? Give feedback.
All reactions