You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, now that Rosetta is used by default on latest macOS, the QEMU issue should no longer be blocking. However, it seems that the issue is still not fixed even when using Rosetta 2. Is there a new upstream issue, now in Rosetta? Or is QEMU still used to some extent?
Context: I'm trying to get k3s amd64 images to work but this fails as explained in this issue: k3s-io/k3s#4720
Reproduce
Make sure Rosetta 2 is enabled in settings in Docker Desktop
Run docker run -it --platform linux/amd64 alpine:latest cat /proc/cpuinfo
Expected behavior
I get the cpuinfo in the layout of the emulated system, looking somewhat like this:
Has anyone figured out a workaround for this issue? Unfortunately Supabase is not compatible with arm64 (at least not Bitnami's docker image for it), which means we need some way of emulating amd64 in our k3d environment.
Description
I'm making a new issue following up on:
/proc/cpuinfo
inside containers reports meaningless data on Apple M1 Max #6111because recent Docker Desktop for Mac releases no longer rely on QEMU.
The issues were closed as "blocked/upstream" pointing at this QEMU issue: https://gitlab.com/qemu-project/qemu/-/issues/750
However, now that Rosetta is used by default on latest macOS, the QEMU issue should no longer be blocking. However, it seems that the issue is still not fixed even when using Rosetta 2. Is there a new upstream issue, now in Rosetta? Or is QEMU still used to some extent?
Context: I'm trying to get k3s amd64 images to work but this fails as explained in this issue: k3s-io/k3s#4720
Reproduce
docker run -it --platform linux/amd64 alpine:latest cat /proc/cpuinfo
Expected behavior
I get the cpuinfo in the layout of the emulated system, looking somewhat like this:
Actual behavior:
I get
docker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.6 API version: 1.43 Go version: go1.20.7 Git commit: ed223bc Built: Mon Sep 4 12:28:49 2023 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.25.1 (128006) Engine: Version: master API version: 1.44 (minimum version 1.12) Go version: go1.21.3 Git commit: 0253fedf03f4964c20906795e119404633cb9c1a Built: Thu Oct 19 08:35:54 2023 OS/Arch: linux/arm64 Experimental: true containerd: Version: 1.6.22 GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca runc: Version: 1.1.8 GitCommit: v1.1.8-0-g82f18fe docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
239B7F30-E6B8-4B1A-BC49-328E5B2FB8AA/20231115030111
Additional Info
If anyone has found a workaround for this general problem of kubernetes amd64 cluster on M1 mac let me know. I'm totally blocked right now.
The text was updated successfully, but these errors were encountered: