Closed arzahs closed 4 months ago
This issue is expected to be resolved with Rosetta support. https://github.com/containers/podman/pull/21670
% podman machine inspect --format {{.Rosetta}}
true
% podman run --rm --arch=amd64 node node --help
Usage: node [options] [ script.js ] [arguments]
node inspect [options] [ script.js | host:port ] [arguments]
Options:
- script read from stdin (default if no
file name is provided, interactive mode
if a tty)
...
Documentation can be found at https://nodejs.org/
@tnk4on But how did it work before? I have another installation with the older machine where it works.
I see the difference only in the machine image. It works on:
But it doesn't work on new machine:
So, after additional testing it works with recent fedora 39 build. When you create machine with hardcoded previous image.
Example:
podman machine init --disk-size 60 --rootful --cpus=4 --memory=8192 --image https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/39.20240407.3.0/aarch64/fedora-coreos-39.20240407.3.0-applehv.aarch64.raw.gz
This is most likely a qemu-user-static regression then if it worked before so you should check rpm -q qemu-user-static
on the working version and the non working version.
sounds like https://gitlab.com/qemu-project/qemu/-/issues/2168
I move this to a discussion as this is not really a podman bug and given the Rosetta implementation should make it in the next version
Issue Description
I got a weird error
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
when trying to run a container withamd64
arch on the arm Macbook after recreating machine with latestmachine init
. It worked well before.Steps to reproduce the issue
The issue is reproducing for me on all mac machines which has an arm processor.
Describe the results you received
I got error with qemo:
Describe the results you expected
podman info output
Additional information
No response