191

I just downloaded Docker Preview v3.1 https://docs.docker.com/docker-for-mac/apple-m1/ and tried running keycloak.

Anyone else running into this issue?

docker run -p 8080:8080 -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin quay.io/keycloak/keycloak:12.0.4
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Etep
  • 2,721
  • 4
  • 17
  • 28

14 Answers14

262

You can try to add this while building the docker images

--platform linux/amd64

from

https://github.com/google/cadvisor/issues/2763

https://github.com/Y2Data

ManojP
  • 6,113
  • 2
  • 37
  • 49
li Etzyio
  • 2,621
  • 2
  • 5
  • 3
  • 52
    Make sure to put this after `docker run` but before the image name btw. – Daniel Porteous May 21 '22 at 18:16
  • 4
    If you are building an image on your M1 Mac to be used on Linux then use the `--platform linux/amd64` to build a version for Intel chips. – RonanCodes Jul 18 '22 at 21:16
  • @DanielPorteous why ? It worked even after appending to the end of the entire command – Uzumaki Naruto Aug 10 '22 at 16:56
  • 2
    what if I am building an image on M1 Mac to run on M1 Mac? Like why won't it still work?! – RedDoumham Dec 03 '22 at 22:10
  • This could work with a warning, depending on the Driver behind your docker-system. I ran it on m1 using Colima, but it uses "emulation" so it's slow and sometimes it `hangs`. It's better just use an arm64 image from this https://hub.docker.com/r/sleighzy/keycloak/tags – Jaekov Segovia Dec 23 '22 at 13:53
  • 4
    for those using docker-compose, you can add `platform: linux/amd64` to the affected images in your `docker-compose.yml` – Stetzon Jan 24 '23 at 17:10
  • This does not work. I tried with an Azure Function project and throws: "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested" – fpuglap Aug 01 '23 at 09:56
45

Add this snipped to your ~/.zshrc and ~/.bashrc. It allows you not to repeat the flag anytime you perform a docker run command:

# useful only for Mac OS Silicon M1, 
# still working but useless for the other platforms
docker() {
 if [[ `uname -m` == "arm64" ]] && [[ "$1" == "run" || "$1" == "build" ]]; then
    /usr/local/bin/docker "$1" --platform linux/amd64 "${@:2}"
  else
     /usr/local/bin/docker "$@"
  fi
}
Alessandro Argentieri
  • 2,901
  • 3
  • 32
  • 62
  • It's probably cleaner to use something like `docker() { if ...; then set "$1" --platform linux/amd64 "${@:2}"; fi; command docker "$@"; }` – William Pursell Jul 01 '23 at 19:10
25

Similar answer to what @li Etzyio replied, the error is telling you that the platform you are using to build the image locally is a different platform than the one used for the image. This happens for M1 computers (and probably other computers), so, what you have to do is specify the --platform <PLATFORM_SPEC> to the docker build command, and replace the <PLATFORM_SPEC> for the one the error is telling you (in this case linux/arm64/v8).

Also something that had worked for me is to set these environment variables:

export DOCKER_BUILDKIT=0                                                                                                                                                    
export COMPOSE_DOCKER_CLI_BUILD=0
export DOCKER_DEFAULT_PLATFORM=linux/amd64

if you don't want to pass the flag --platform every-time you run the build command.

anothermh
  • 9,815
  • 3
  • 33
  • 52
Cesar Flores
  • 762
  • 7
  • 16
  • Thank you sir. Just bought an M1 Pro and this helped me with Docker Compose, or rather images that I'm consuming, not building. Also confirming that I'm using docker compose v2 and file version v3 – DevOverlord Jan 08 '23 at 03:33
  • Best answer in this post, thanks – Thales Valias Jan 25 '23 at 12:11
  • Thanks. Just this line was enough for this: `export DOCKER_DEFAULT_PLATFORM=linux/amd64`. And to add it to a script used by different people, I added `export DOCKER_DEFAULT_PLATFORM=linux/$(uname -m)` – juanesarango Jul 14 '23 at 16:53
  • How do you set the environment variable? do you just run export DOCKER_DEFAULT_PLATFORM=linux/amd64 in the terminal? – Sayf Aug 25 '23 at 09:25
  • 1
    @Sayf yes just type in the terminal or add it in your shell file – Cesar Flores Aug 26 '23 at 21:52
20

If you run Docker Workstation on an M1 mac, you can leverage the Docker Workstation multi-CPU architecture support, which includes the buildx command. It allows you to create images for different CPUs.

To build a Linux/AMD/Intel image on your M1 mac workstation, run the following.

docker buildx build --platform=linux/amd64 -t myorg/mytag:1.0.0 .

Placing docker buildx in front starts the command with BuildKit. See the links above for details.

pglezen
  • 961
  • 8
  • 18
  • 1
    Thanks! This helped me deploy images I build on my M1 mac to https://labs.play-with-docker.com/ – Shiraz Oct 04 '22 at 14:20
  • Great answer; I was building the image on an M1 Mac and needing it to run in Jenkins (Linux). After doing it this way, Jenkins had no problem using the image. Thanks! – mmarion Dec 16 '22 at 23:33
  • This helped me get the docker getting-started app on play-wtih-docker as well. I ran into other issues, the build was taking very long. Eventually debugged to get npm to not audit `RUN npm install --production --no-audit` in the Dockerfile. I also had to add the flag --network="host" at the end of the command. `docker buildx build --platform=linux/amd64 -t getting-started . --network="host"` – OctaviaLo Dec 22 '22 at 04:17
13

Just found this post: https://github.com/docker/for-mac/issues/5310#issuecomment-779791882

Using this image, I am now able to startup keycloak. https://hub.docker.com/r/wizzn/keycloak

Etep
  • 2,721
  • 4
  • 17
  • 28
10

On Mac using M1 you need to Enable Rosetta in Docker Desktop (Settings > Features in development). Rosetta is a dynamic binary translator for Mac silicon that allows x86 instructions to be translated into ARM instructions.

enter image description here

You can then specify the default Docker build configuration by setting the following environment variable (note - only do this if you want all Docker containers to use this as the default platform):

export DOCKER_DEFAULT_PLATFORM=linux/amd64

When you next run a Docker build, it will use this as the default platform for the images, and with Rosetta enabled it should now work.

See - https://collabnix.com/warning-the-requested-images-platform-linux-amd64-does-not-match-the-detected-host-platform-linux-arm64-v8/

Chris Halcrow
  • 28,994
  • 18
  • 176
  • 206
  • Thank you! You saved my day! I tried to run keycloak 13.0.1 and got failed with any other approaches: making my own build, using flag --platform, and many others. – donmaro Jul 26 '23 at 19:43
6

The following will do the trick when building images on M1 machines:

docker build -t <image-name> --platform linux/x86_64
Giorgos Myrianthous
  • 36,235
  • 20
  • 134
  • 156
3

I also had this problem when I upgraded to a new version

I fix it by delete all images was builded by old version "docker system prune --all" and re build image

longhust
  • 31
  • 1
  • this is the easiest and best solution if you end up here after installing an M1 mac from a time machine backup that had all amd64 images!!! – Edoardo Feb 15 '23 at 15:20
2

Setting the "Use Rosetta for x86/amd64 emulation on Apple Silicon" config in the docker desktop helped me resolve this issue - Docker Setting

  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jul 17 '23 at 12:21
1

The root cause the same as in the following threads:

Forcing docker to use linux/amd64 platform by default on macOS

Docker on Mac M1 gives: "The requested image's platform (linux/amd64) does not match the detected host platform"

There is a 'fix' for docker-compose.yml approach as well.

Maksym Kosenko
  • 515
  • 7
  • 12
0

For me, the error happened because I build the docker image on an M1 chip Macbook, and tried to run the image on a Linux machine.

This worked for me:

Build the docker image using the same machine that needs to run it, and it worked.

C.Lee
  • 10,451
  • 9
  • 31
  • 46
  • 14
    This defeats the primary reason for using docker containers. – Peter Moses Jul 18 '22 at 01:03
  • @PeterMoses well, kind of, but in my case, I have to run the same docker container on multiple servers / worker-nodes, so the answer solves the exact problem for me. – C.Lee Jul 19 '22 at 05:52
0

I had this issue because in my Dockerfile i used FROM java:8 which doesn't support arm64.

I fix it by running the following command:

docker pull openjdk

then changed my Dockerfile to

FROM openjdk:latest
eNca
  • 1,043
  • 11
  • 21
tcon163
  • 11
-2

This solves the porblem in Mac too

docker pull openjdk then changed my Dockerfile to

FROM openjdk:latest