Crash with rosetta in 0.6.0 (regression from 0.5.6) about colima HOT 13 CLOSED

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)

from colima.

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. 🤷

from colima.

Sonoma 14.1 on an m1 mac mini.

from colima.

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

from colima.

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.

from colima.

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

from colima.

This actually worked for me.

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

from colima.

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...

from colima.

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

from colima.

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 ?

from colima.

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!!

from colima.

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?

from colima.

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

from colima.