Multi-Architecture Container Images: Why Bother, and How To
summary
Demonstrates how to build and publish a single image name that serves both amd64 and arm64 by building per-architecture images, editing their JSON config to set architecture, pushing to Docker Hub, then creating a manifest list with the experimental docker manifest create and testing pulls with the --platform flag; automation reduces the painful ~30 manual steps into a Makefile. Explains why go-containerregistry defaults to amd64 and how that breaks CI pipelines like Kaniko and ko.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:31BUT LISA, HOW DO I GET AN IMAGE??
- 14:48DOCS AND CULTURE SAY ONE THING WHILE IMAGES SAY ANOTHER
- 29:38WHY BOTHER?
- 35:31CREATE & DISTRIBUTE
- 36:13UNDERSTAND THE CULTURE AND GOALS TILT TOWARDS CROSS-PLATFORM
related talks
37mWhy are multi-architecture images important?
15mBuilding multi-arch container images with buildah
38mRunning Multi-Arch Builds & Tests in OpenShift CI/CD
25mBuilding Docker Images Without Docker
27mWhat's Going ARM: Adopting ARM64 At Airbnb
40mContainers on the Edge: Deploying Embedded Linux Systems With Modern D...
29mDockerfile: the best practices
34mDefence Against the Docker Arts