uncaught target signal 11 (Segmentation fault) - core dumped, running a container on MacOS with M1 chip

Error Unable to start a container on new MacBook Pro with M1 chip

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
ERRO[0553] error waiting for container: invalid character 'u' looking for beginning of value...

Reproduce

docker run -p 9090:9090 -p 9191:9191 -t adobe/s3mock

System macOS Big Sur v11.1 Apple M1 chip

Relevant issue Quoted from here

This is a qemu bug, which is the upstream component we use for running Intel (amd64) containers on M1 (arm64) chips, and is unfortunately not something we control. In general we recommend running arm64 containers on M1 chips because (even ignoring any crashes) they will always be faster and use less memory.

Please encourage the author of this container to supply an arm64 or multi-arch image, not just an Intel one. Now that M1 is a mainstream platform, we think that most container authors will be keen to do this.

[aleixmorgadas]

I’ve been trying to build the image by my own, but I failed 😅

I also tried building the image in a Linux machine targeting arm64/v8 but I think I would need more time to succeed.

PD: I had that much troubles using M1 chip that I just changed the laptop to use Intel i7 again. Whole Development ecosystem not ready to use M1.

[afranken]

just released version 2.4.6 which is multi arch for arm64 and amd64. https://hub.docker.com/r/adobe/s3mock/tags?page=1&ordering=last_updated