Error response from daemon: no matching manifest for linux/mips64le in the manifest list entries: no match for platform in manifest: not found means the image exists, but its publisher did not build it for the platform you asked for. List the platforms the tag offers with docker buildx imagetools inspect and pick one of them, or choose an image that is built for your platform.

In the test the tag existed and was already cached; only the value after --platform had no match in the image's list of platforms.

The error

PS> docker pull --platform linux/mips64le alpine:latest
Error response from daemon: no matching manifest for linux/mips64le in the manifest list entries: no match for platform in manifest: not found
exit code: 1

Why it happens

A tag such as alpine:latest points at a list of images, one per platform. The pull asked for linux/mips64le, and the list had no entry for it, so the daemon stopped before downloading anything: no Pulling from line was printed. The cached alpine:latest was not changed by the failed pull; docker image ls alpine showed the same image id, 294b683cb724, before and after.

To see what the list does contain, inspect it. The command reads the list from the registry and changes nothing locally. The output is long; these are its Platform lines: 

PS> docker buildx imagetools inspect alpine:latest
...
  Platform:    linux/amd64
...
  Platform:    linux/arm/v6
...
  Platform:    linux/arm/v7
...
  Platform:    linux/arm64/v8
...
  Platform:    linux/386
...
  Platform:    linux/ppc64le
...
  Platform:    linux/riscv64
...
  Platform:    linux/s390x
...

Between them the output shows entries with Platform: unknown/unknown; their annotations name them attestation-manifest and point at the image entry before them. linux/mips64le is not in the list, which matches the error.

The fix

PS> docker pull --platform linux/amd64 alpine@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
docker.io/library/alpine@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6: Pulling from library/alpine
Digest: sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
Status: Image is up to date for alpine@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
docker.io/library/alpine@sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
exit code: 0

With a platform from the list the pull succeeded. The test pulled by digest so the cached alpine:latest tag stayed as it was; docker pull --platform linux/amd64 alpine:latest is the everyday form. If the platform you need is not in the list at all, no value of --platform will fetch it from that tag: look for another image whose list contains it.

How it was reproduced

On Windows 11 with Docker Desktop, client and engine 29.9.3, buildx v0.38.1, in PowerShell 5.1: docker pull --platform linux/mips64le alpine:latest with alpine:latest already cached (image id 294b683cb724), then docker image ls alpine and the read-only docker buildx imagetools inspect alpine:latest. The list was read on Nov 10, 2026, when its entries were labelled version 3.24.4.

Frequently asked

What does 'no matching manifest for linux/... in the manifest list entries' mean?
The image tag exists, but it has no image for the platform requested. Run docker buildx imagetools inspect on the tag to see which platforms it offers.
How do I see which platforms a Docker image supports?
docker buildx imagetools inspect <image:tag> prints one Platform line per image in the list. It reads the registry and changes nothing on your machine.
Does a failed docker pull --platform replace my cached image?
Not in this test. The pull failed before downloading anything, and docker image ls showed the same image id for alpine:latest before and after.

More decoded errors in the Fixes category.