How to fix Error response from daemon: no matching manifest for linux/amd64 in the manifest list entries in Docker

What this error means

This error indicates that Docker's registry API returned a manifest list (also known as a fat manifest) that doesn't include a variant for the linux/amd64 architecture. A manifest list is an index pointing to multiple platform-specific image manifests, allowing registries to serve the correct image variant based on the client's architecture. When you pull an image, Docker sends your system's platform information (OS and architecture) to the registry. The registry looks up the manifest list for the requested image tag and tries to find a matching entry. If no entry exists for linux/amd64, this error is returned. This commonly happens when: - An image was built exclusively for ARM architecture (common with Raspberry Pi images) - The image maintainer hasn't published a linux/amd64 variant - You're using a tag that is temporarily unavailable or being rebuilt - The Docker Hub "latest" tag is being updated and momentarily missing architectures Unlike the related "platform mismatch" warning (which allows containers to run under emulation), this error completely blocks the image pull because Docker cannot find any variant to download.

Typical symptoms

• docker pull fails with 'no matching manifest for linux/amd64 in the manifest list entries'
• docker run fails immediately without starting the container
• Dockerfile builds fail during FROM instruction when base image lacks amd64 support
• CI/CD pipelines fail on x86 runners when using ARM-only images
• Docker Compose up fails to start services using incompatible images
• Multi-stage builds fail when a stage uses an ARM-only base image
• Error appears after an image tag was updated or renamed on the registry

Common causes

1. The image was built exclusively for ARM architecture (arm64, arm/v7) and doesn't include an amd64 variant
2. Using the 'latest' tag while the image is being rebuilt on Docker Hub - architecture manifests may be temporarily unavailable
3. The specific image tag was removed, renamed, or never included an amd64 build
4. The image is from a registry with incomplete multi-architecture support
5. Image maintainer deprecated x86 builds in favor of ARM-only releases
6. Docker attestation issues in GitHub Actions causing manifest list problems during push
7. Registry rate limiting or network issues preventing manifest retrieval
8. Using Docker Desktop with 'Use containerd for pulling and storing images' enabled (can cause manifest resolution issues)

How to fix "Error response from daemon: no matching manifest for linux/amd64 in the manifest list entries"

# Using docker buildx imagetools (recommended)
docker buildx imagetools inspect IMAGE:TAG

# Alternative: Using manifest inspect
docker manifest inspect IMAGE:TAG

# Parse with jq to see just platforms
docker manifest inspect IMAGE:TAG | jq '.manifests[].platform'

{
  "architecture": "amd64",
  "os": "linux"
}
{
  "architecture": "arm64",
  "os": "linux"
}

# Instead of 'latest', use a specific version
docker pull postgres:15  # instead of postgres:latest

# Check for architecture-specific tags
docker pull nginx:1.25-alpine-amd64  # if available

# Look for '-amd64' or '-x86_64' suffixed tags
docker pull some-image:v1.0-amd64

# Search Docker Hub for similar images
docker search IMAGE_NAME

# Check official images first - they usually support multiple architectures
docker buildx imagetools inspect nginx:latest
docker buildx imagetools inspect python:3.11

# Dockerfile
FROM --platform=linux/amd64 alpine:latest
# Or use a multi-arch base and let Docker select
FROM alpine:latest

RUN apk add --no-cache your-packages
COPY . /app
CMD ["./app"]

# Create a builder for multi-platform builds
docker buildx create --name mybuilder --use --bootstrap

# Build for multiple architectures
docker buildx build \
  --platform linux/amd64,linux/arm64 \
  --tag your-registry/your-image:latest \
  --push \
  .

# After restart, verify the setting
docker info | grep "Storage Driver"
# Should show: overlay2 (not containerd)

# Try pulling the image again
docker pull IMAGE:TAG

# Remove all unused images, containers, networks, and cache
docker system prune -a

# Clear the buildx cache specifically
docker buildx prune -a

# Pull with explicit no-cache flag
docker pull --no-cache IMAGE:TAG

# Alternative: Remove specific image and repull
docker rmi IMAGE:TAG
docker pull IMAGE:TAG

# .github/workflows/docker.yml
- name: Build and push
  uses: docker/build-push-action@v5
  with:
    platforms: linux/amd64,linux/arm64
    push: true
    tags: user/app:latest
    # Disable attestation to fix manifest issues
    provenance: false
    sbom: false

docker buildx build \
  --platform linux/amd64,linux/arm64 \
  --provenance=false \
  --sbom=false \
  --push \
  -t your-image:tag .

# Install QEMU handlers for cross-architecture execution
docker run --privileged --rm tonistiigi/binfmt --install all

# Try pulling with explicit ARM platform
docker pull --platform linux/arm64 IMAGE:TAG

# Run the ARM image under emulation
docker run --platform linux/arm64 IMAGE:TAG

Advanced notes

image:tag
  └── manifest list (application/vnd.docker.distribution.manifest.list.v2+json)
        ├── linux/amd64 manifest → layers for x86_64
        ├── linux/arm64 manifest → layers for ARM 64-bit
        └── linux/arm/v7 manifest → layers for ARM 32-bit

# Get raw manifest from registry (requires authentication for private images)
curl -s -H "Accept: application/vnd.docker.distribution.manifest.list.v2+json" \
  "https://registry-1.docker.io/v2/library/nginx/manifests/latest" | jq

# Check what Docker thinks your platform is
docker info --format '{{.OSType}}/{{.Architecture}}'

# Inspect local image platform
docker image inspect IMAGE:TAG --format '{{.Os}}/{{.Architecture}}'

# Enable Docker CLI debugging
DOCKER_CLI_EXPERIMENTAL=enabled docker manifest inspect IMAGE:TAG

# This only keeps ONE architecture locally (last built or native)
docker buildx build --platform linux/amd64,linux/arm64 --load .

# To get a proper manifest list, you must push to a registry
docker buildx build --platform linux/amd64,linux/arm64 --push -t registry/image:tag .

# Or use the containerd image store (Docker Desktop)
docker buildx build --platform linux/amd64,linux/arm64 --load .

Frequently asked questions

What does "Error response from daemon: no matching manifest for linux/amd64 in th" mean?

This error indicates that Docker's registry API returned a manifest list (also known as a fat manifest) that doesn't include a variant for the linux/amd64 architecture. A manifest list is an index pointing to multiple platform-specific image manifests, allowing registries to serve the correct image variant based on the client's architecture. When you pull an image, Docker sends your system's platform information (OS and architecture) to the registry.

How do I fix "Error response from daemon: no matching manifest for linux/amd64 in th"?

This error occurs when Docker cannot find an image variant built for your system's CPU architecture (linux/amd64). Common when pulling ARM-only images on Intel/AMD machines, or when using outdated tags. Fix by specifying the correct platform, finding multi-arch images, or building your own.

What causes "Error response from daemon: no matching manifest for linux/amd64 in th"?

The image was built exclusively for ARM architecture (arm64, arm/v7) and doesn't include an amd64 variant Using the 'latest' tag while the image is being rebuilt on Docker Hub - architecture manifests may be temporarily unavailable The specific image tag was removed, renamed, or never included an amd64 build

Is the "Error response from daemon: no matching manifest for linux/amd64 in th" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Error response from daemon: no matching manifest for linux/arm64 in the manifest list entries

  How to fix 'no matching manifest for linux/arm64' in Docker

  MEDIUM

• Error response from daemon: no matching manifest for linux/arm64/v8 in the manifest list entries

  How to fix 'no matching manifest for linux/arm64' in Docker

  MEDIUM

• Error response from daemon: operation not permitted (no-new-privileges)

  How to fix 'operation not permitted (no-new-privileges)' in Docker

  MEDIUM

• failed to solve: failed to compute cache key: failed to calculate checksum: no build stage in current context

  How to fix 'no build stage in current context' in Docker

  MEDIUM

• WSL 2 requires an update to its kernel component

  How to fix 'WSL 2 requires an update to its kernel component' in Docker

  MEDIUM

• dial tcp: i/o timeout

  How to fix 'dial tcp: i/o timeout' in Docker

  MEDIUM

Official resources & further reading

• 📚Docker Official Documentation
• 📖
  Docker Docs - Multi-platform builds(Official Docs)
• 💬
  Docker Forums - No matching manifest discussion(Stack Overflow)
• 💬
  CircleCI Support - Manifest list entries error(Stack Overflow)
• 💬
  Stack Overflow - Multi-arch manifest push issues(Stack Overflow)
• 🐙
  GitHub - Node.js Docker manifest issue(GitHub)
• 📝
  Kontext - Docker manifest error explanation
• 📝
  100 Common Docker Errors & Solutions