Open DrBushyTop opened 2 years ago
Maybe similar to issues we have since QEMU v7, can you try with v6.2.0:
$ docker run --rm --privileged tonistiigi/binfmt --uninstall qemu-*
$ docker run --rm --privileged tonistiigi/binfmt:qemu-v6.2.0 --install all
Thanks for the good suggestion, but unfortunately this did not have any effect.
Not sure if this is 100% related but I get segmentation faults when on a Mac M1 Pro (arm64) I build a docker image for --platform=linux/amd64
project: a Ruby application that uses dependencies that require native extensions to be compiled in C, 9/10 cases end up with segmentation fault, but every now and then it works so this is clearly a bug in Docker/buildx/qemu
gcc: internal compiler error: Segmentation fault signal terminated program cc1
I've confirmed that this is also a problem going in the opposite way: trying to build linux/arm64 on an amd64 system also causes the very same segfault.
UPDATE: I tested with QEMU 7.1.0, 7.0.0, 6.2.0, 6.1.0, 6.0.0, 5.2.0, all failed.
I build an image of linux/amd64
architecture on arm64 server, the source code comes from ImageMagick, and this error also occurs.
I want to know, do you have a solution? If the other way around, building linux/arm64/v8
on amd64 is successful.
Hi, I recently updated my M1 Max Macbook to Ventura, as well as the newest Docker Desktop version, and my previously building dockerfiles now fail on seemingly any Powershell module installation with either
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
or target signal 6. It's been 1,5 months since I last built this specific image, so it's not necessarily related to either of the mentioned updates though.Some specs: MacOS version: 13.0.1 (22A400) Docker Desktop Version: 4.14.1 (91661)
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check produces no fatal errors.
Building on ARM64 passes this fine.
Output from build:
Here's the output for another module (Microsoft.Graph)
Example Dockerfile
Any ideas? Thanks!