Can't run amd64 .sif in macOS/aarch64 rosetta mode

[n-io]

I have been running an sdk that comes packaged in a .sif file. The sif is built for amd64, and I am using qemu system mode to run it on my macOS/aarch64. E.g.:

limactl start template://apptainer --vm-type=qemu --arch=x86_64 --mount-writable --set '.cpuType.x86_64="max"' --name apptainer

Without the cpuType option, it will error saying Illegal instruction (core dumped). With the cpuType option, the above approach works fine but is somewhat slow for bigger tasks. I've tried other ways of running it, but so far without success. For instance:

limactl start template://apptainer --vm-type=vz --rosetta --mount-writable --set '.rosetta.binfmt=true' --mount-type=virtiofs --set '.cpuType.x86_64="max"' --name apptainer

I've tried config different options, but the result is mostly the same: I can get a shell via singularity shell /path/to/sdk.sif, browse around and vim into some files, but when I attempt to run any of the main apps in the container, it will error saying Illegal instruction (core dumped). I'm not sure how to go about diagnosing or fixing this, or whether this is the right approach?

[afbjorklund]

I think it is related to that we reverted to a v1 cpu for a while, but it should soon be back to a v3 cpu.

• qemu: Intel on ARM: change the default CPU from qemu64 to something newer #3063

You might have better performance when running qemu-user or Rosetta, instead of emulating the OS?

[n-io]

You might have better performance when running qemu-user or Rosetta, instead of emulating the OS?

I'd love to, this is what I'm trying to do, unsuccessfully though. So far, I've only managed to get the qemu system mode to work (first option above), but not the rosetta mode. I might need some assistance with this please.

[afbjorklund]

• Can't run amd64 apptainer in rosetta-mode apple silicon mac #3135

[n-io]

I had seen this, but had concluded that in my best understanding they are trying to do something different (building a sif rather than running an existing one) and encountered a different problem.

[afbjorklund]

You should report the bugs you are getting, it seemed to work out of the box for me.

[n-io]

Thanks, raised as #3195

[afbjorklund]

Without the cpuType option, it will error saying Illegal instruction (core dumped).

The default cpuType is supposed to work, especially on ubuntu (the v1 affected RHEL)