Mike Belveder

03/02/2022, 9:45 AM
Hi! Do you understand what am I doing wrong here? I’m using Apple Silicon.
👀 1


03/02/2022, 9:57 AM
Hi @Mike Belveder! The problem here is correctly indicated by the warning:
The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/8)
Our images are non-multi-architecture images, only running on
. So you are not doing anything wrong here ;) @Rick Lamers Started to work on making them multi-arch. What is the status on this?
Some additional information can be found under item 2 at
Not all images are available for ARM64 architecture. You can add
--platform linux/amd64
to run an Intel image under emulation. In particular, the mysql image is not available for ARM64. You can work around this issue by using a mariadb image.
However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as qemu sometimes fails to run the container. In addition, filesystem change notification APIs (
) do not work under qemu emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent.
In summary, running Intel-based containers on Arm-based machines should be regarded as “best effort” only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers. We expect this issue to become less common over time, as more and more images are rebuilt supporting multiple architectures.
From your side there isn't anything you can do to make this work on your machine (at this time). Alternatively, you can request a free instance on our cloud offering ( and I will make sure you are approved asap. Sorry for the inconvenience.

Rick Lamers

03/02/2022, 10:07 AM
I can confirm running under emulation does work on macOS arm64. We're planning multiple improvements of the container image stack including arm64 support and minification. Those are both still WIP though, as it requires some changes to upstream OSS we include.
👍 2
We don't currently specify architecture for our
docker run
invocation. So it might be necessary to add it (
--platform linux/amd64
) to the orchest entrypoint manually (
bash file in the root of the repo). Since we're porting to k8s we are no longer actively updating the current Docker container orchestration code beyond the amd64 support.


03/02/2022, 10:32 AM