Multi-Architecture Images
You'll learn how manifest lists let a single image tag work seamlessly across different CPU architectures.
The Architecture Challenge
Containers run on many different CPU types: Intel/AMD x86_64, ARM processors in mobile and edge devices, Apple Silicon (ARM64), and more. Without multi-architecture support, you'd need separate image tags like myapp:v1-amd64 and myapp:v1-arm64, forcing users to pick the right one manually.
How Manifest Lists Solve This
A manifest list (also called an "image index") is a special pointer that sits above individual architecture-specific images. When you pull myapp:v1, the container runtime checks your CPU architecture and the manifest list automatically routes you to the correct underlying image.
Think of it like a restaurant menu with language options: everyone sees "Menu" on the cover, but opening it reveals the right language for each customer. One name, multiple versions served automatically.
The Structure
myapp:v1 (manifest list)
├── myapp@sha256:abc123... (linux/amd64)
├── myapp@sha256:def456... (linux/arm64)
└── myapp@sha256:ghi789... (linux/arm/v7)
When you reference myapp:v1, the runtime transparently selects the digest matching your platform. You never need to know which architecture you're on—the manifest list handles it.
Why This Matters
Multi-architecture images enable true portability. The same docker pull myapp:v1 command works on your Intel laptop, ARM-based cloud instances, and Raspberry Pi devices. Developers build once, and users run anywhere without modifying scripts or deployment configurations.
Key Takeaway:
Manifest lists enable a single image tag to automatically serve the correct architecture-specific image, making containers truly portable across different CPU types without user intervention.