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

What this error means

This error indicates that the Docker image you're trying to pull doesn't have a version compiled for the ARM64 CPU architecture. Docker images are built for specific processor architectures, and when Docker requests an image from a registry like Docker Hub, it looks for a manifest that matches your system's architecture. On ARM64 systems (Apple Silicon Macs, Raspberry Pi 4, AWS Graviton, and other ARM-based devices), Docker looks for images tagged with `linux/arm64` or `linux/arm64/v8`. When the image maintainer only provides builds for Intel/AMD processors (`linux/amd64`), Docker cannot find a matching manifest entry and throws this error. This is particularly common with older images, specialized tools, or software that hasn't been ported to ARM yet. The issue became more prevalent with the release of Apple Silicon Macs (M1/M2/M3/M4 chips) and the growing adoption of ARM-based servers for their power efficiency.

Typical symptoms

• Error: 'no matching manifest for linux/arm64/v8 in the manifest list entries' when pulling images
• Docker pull fails on Apple Silicon Mac (M1/M2/M3/M4)
• Docker Compose fails to start services on Raspberry Pi
• CI/CD pipelines fail on ARM-based runners (AWS Graviton, GitHub Actions ARM)
• Images that work on Intel Macs or x86 Linux servers fail on ARM machines
• The same docker-compose.yml works on some team members' machines but not others
• Error occurs immediately during 'docker pull' or 'docker run' commands

Common causes

1. The image maintainer only published amd64 (Intel/AMD) builds without ARM64 support (most common)
2. Using an older image version that predates ARM64 support
3. Pulling from a private registry that only contains amd64 images
4. The image uses base layers that are not available for ARM64
5. Specifying an image tag that only has amd64 variants (e.g., some '-alpine' or version-specific tags)
6. Image was built without multi-architecture support using older Docker build methods
7. Third-party or community images that haven't been updated for ARM compatibility

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

# Pull the amd64 version explicitly
docker pull --platform linux/amd64 mysql:5.7

# Run with platform specification
docker run --platform linux/amd64 mysql:5.7

# Works for any image without ARM support
docker run --platform linux/amd64 <image-name>:<tag>

# docker-compose.yml
version: '3.8'
services:
  mysql:
    image: mysql:5.7
    platform: linux/amd64  # Force amd64 with emulation
    ports:
      - "3306:3306"
    environment:
      MYSQL_ROOT_PASSWORD: secret

  redis:
    image: redis:alpine  # Has native ARM64 support - no platform needed
    ports:
      - "6379:6379"

# Set for current terminal session
export DOCKER_DEFAULT_PLATFORM=linux/amd64

# Add to shell profile for persistence
# For zsh (default on macOS):
echo 'export DOCKER_DEFAULT_PLATFORM=linux/amd64' >> ~/.zshrc
source ~/.zshrc

# For bash:
echo 'export DOCKER_DEFAULT_PLATFORM=linux/amd64' >> ~/.bashrc
source ~/.bashrc

unset DOCKER_DEFAULT_PLATFORM

# Inspect available platforms for an image
docker buildx imagetools inspect mysql:latest

# Example output showing multi-arch support:
# Name:      docker.io/library/mysql:latest
# Platforms: linux/amd64, linux/arm64/v8

# mysql:5.7 has no ARM support, but mysql:8.0+ does
   docker pull mysql:8.0

docker pull arm64v8/mysql
   docker pull arm64v8/nginx

# MariaDB as MySQL alternative (has ARM64 support)
   docker pull mariadb:latest

# Option 1: Install QEMU packages (Ubuntu/Debian)
sudo apt-get update
sudo apt-get install -y qemu-user-static binfmt-support

# Option 2: Use Docker's QEMU image (works on any Linux)
docker run --privileged --rm tonistiigi/binfmt --install all

# Verify QEMU is registered
ls /proc/sys/fs/binfmt_misc/qemu-*

# Test amd64 emulation
docker run --platform linux/amd64 alpine uname -m
# Should output: x86_64

# After restart, verify Rosetta is being used
docker run --platform linux/amd64 alpine uname -m
# Should output: x86_64

# Create and use a builder that supports multi-platform
docker buildx create --name multiarch-builder --use --bootstrap

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

# Verify the multi-arch manifest
docker buildx imagetools inspect your-registry/your-image:latest

Advanced notes

# Add to ~/.zshrc or ~/.bashrc
check_platforms() {
  docker buildx imagetools inspect "$1" 2>/dev/null | grep -A 20 "Manifests:" || echo "Image not found or no manifest list"
}

# Usage
check_platforms nginx:latest
check_platforms mysql:5.7

# GitHub Actions example
name: Build Multi-Arch
on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          platforms: linux/amd64,linux/arm64
          push: true
          tags: user/app:latest

FROM alpine:latest

# Use build argument to detect architecture
ARG TARGETARCH

# Download architecture-specific binary
RUN wget https://example.com/tool-${TARGETARCH}.tar.gz && \
    tar xzf tool-${TARGETARCH}.tar.gz

# TARGETARCH will be 'amd64' or 'arm64' based on build platform

# Option 1: Use MySQL 8 (has ARM64 support)
services:
  db:
    image: mysql:8.0

# Option 2: Use MariaDB (drop-in replacement, ARM support)
services:
  db:
    image: mariadb:10.11

# Option 3: Emulate MySQL 5.7 if required
services:
  db:
    image: mysql:5.7
    platform: linux/amd64

Frequently asked questions

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

This error indicates that the Docker image you're trying to pull doesn't have a version compiled for the ARM64 CPU architecture. Docker images are built for specific processor architectures, and when Docker requests an image from a registry like Docker Hub, it looks for a manifest that matches your system's architecture. On ARM64 systems (Apple Silicon Macs, Raspberry Pi 4, AWS Graviton, and other ARM-based devices), Docker looks for images tagged with linux/arm64 or linux/arm64/v8.

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

This error occurs when pulling a Docker image that doesn't have a variant for your ARM64 architecture (Apple Silicon, Raspberry Pi, AWS Graviton). The fix involves using the --platform flag to emulate amd64, finding ARM-compatible images, or building multi-architecture images with Docker Buildx.

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

The image maintainer only published amd64 (Intel/AMD) builds without ARM64 support (most common) Using an older image version that predates ARM64 support Pulling from a private registry that only contains amd64 images

Is the "Error response from daemon: no matching manifest for linux/arm64 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: operation not permitted (no-new-privileges)

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

  MEDIUM

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

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

  MEDIUM

• dial tcp: lookup host.docker.internal: no such host

  How to fix 'lookup host.docker.internal: no such host' 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

• 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 Blog - Building Multi-Arch Images(Official Docs)
• 💬
  Stack Overflow - Docker Apple Silicon MySQL ARM64 error(Stack Overflow)
• 💬
  Stack Overflow - No matching manifest for linux/arm64/v8(Stack Overflow)
• 💬
  Docker Forums - Manifest lists linux/arm64 discussion(Stack Overflow)
• 📝
  DevCoops - Apple M1 Chip Docker Error solution
• 📝
  100 Common Docker Errors & Solutions
• 📝
  KhueApps - Fix no matching manifest errors