Crash with rosetta in 0.6.0 (regression from 0.5.6)

[lejoko]

Description

Crash in Rosetta when running official mysql:5.7 image:

$ docker run -it --rm mysql:5.7
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
rosetta error: unhandled auxillary vector type 28
$

Version

Colima Version: 0.6.0
Lima Version: 0.18.0
Qemu Version: 8.1.2

Operating System

• macOS Intel <= 12 (Monterrey)
• macOS Intel >= 13 (Ventura)
• macOS M1 <= 12 (Monterrey)
• macOS M1 >= 13 (Ventura)
• Linux

Output of colima status

$ colima status -p rosetta
INFO[0000] colima [profile=rosetta] is running using macOS Virtualization.Framework 
INFO[0000] arch: aarch64                                
INFO[0000] runtime: docker                              
INFO[0000] mountType: virtiofs                          
INFO[0000] socket: unix:///Users/joel/.colima/rosetta/docker.sock 
$ cat ~/.colima/rosetta/colima.yaml |grep -v "^ *#\|^ *$"
cpu: 8
disk: 60
memory: 8
arch: aarch64
runtime: docker
hostname: colima
kubernetes:
  enabled: false
  version: v1.28.3+k3s2
  k3sArgs:
    - --disable=traefik
autoActivate: true
network:
  address: false
  dns: []
  dnsHosts: {}
forwardAgent: false
docker: {}
vmType: vz
rosetta: true
mountType: virtiofs
mountInotify: true
cpuType: ""
provision: []
sshConfig: true
mounts: []
env: {}
$

Reproduction Steps

1. Start colima with rosetta activated (as per described config)
2. run docker run -it --rm mysql:5.7
3. observe rosetta crashing

Expected behaviour

A running mysql 5.7 container

Additional context

It used to work in Colima 0.5.6

[lejoko]

Tested with (just upgraded) Colima 0.6.1 in the same conditions as above and nothing changed.

[abiosoft]

This actually worked for me.

docker run -it --rm --platform linux/amd64 mysql:5.7

[lejoko]

I'm on a M2 MacBook Pro With Ventura 13.6.2, all updates applied to both system and brew. Are you maybe on Sonoma ? I was reluctant to upgrade to Sonoma...

[abiosoft]

@lejoko ideally you should specify the --platform linux/amd64 flag.

[lejoko]

It's the same with the --platform linux/amd64. It only removes the warning, but it still crash with the same error. On what OS version did you test ?

[abiosoft]

Sonoma 14.1 on an m1 mac mini.

[tmapes]

I ran into this on a different image (but could actually run mysql:5.7 fine) on 13.6.

Seems like it was fixed by Apple in 14.1

[lejoko]

Apparently it also works for me with Sonoma 14.1.1. That specific problem seem to exist only with Ventura. I'm currently testing other potentially problematic images.

By the way, big thanks for Colima!!

[elementalvoid]

Someone on my team has also experienced this with an AMD64 MySQL container running on an ARM Mac and the vz/rosetta hypervisor.

There's a similar report and some good insights from another project here: utmapp/UTM#5567. They also note that Sonoma 14.1 fix!

---

Edit: I have also confirmed that my teammate is not on Sonoma.

[lejoko]

Ok. Everything related to Colima works for me with Sonoma 14.1.1 (I still have crashes with rosetta but they're not related to Colima)

[Westacular]

This comment indicates that the issue was fixed in UTM for a macOS 13.5.1 user by adding --preserve yes to the update-binfmts command.

The relevant Apple documentation effectively says to use --preserve yes for macOS 14 but --preserve no on macOS 13, somewhat contradicting that solution.

Colima doesn't use update-binfmts, and instead injects the equivalent string to binfmt_misc directly, here. The string it's using does not include the P flag (see docs), so it is doing the equivalent of --preserve no.

I'm curious what would happen if that were changed by adding the P flag.

Things are already working in macOS 14, where the Apple docs suggest it should be added; things aren't working in macOS 13 where the Apple docs suggest it should not be added, but anecdotally, adding it does fix this issue. 🤷

[Curtisjk]

I came across this issue today with colima 0.6.7 and Ventura 13.6.3, so is definitely not fixed.

Does anyone know how to apply a workaround?

[yous]

Direct use of lima doesn't have this issue in Ventura.