Demystifying Container Images: Understanding Multi-Architecture, Manifests, IDs, and Digests
summary
Local builds produce separate digests for manifest, config (image ID) and each layer, and pushing to a registry often changes the manifest digest because registries gzip or reserialize manifests so the digest differs from the local tarball version. Podman and Builder are used, Quay hosts registries, and podman manifest creates a multi-architecture image index that links per-architecture manifests so an x86 image won’t run on ARM without the index. digest changes when registry gzips manifests use registry digest as source of truth podman manifest creates image index
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:29Container image lifecycle overview
- 2:56Open Container Initiative standards
- 4:00Manifest files and digests
- 8:54Image IDs and registry push
- 10:22Digest changes after pushing
- 13:15Multi-architecture challenges
- 14:41Multi-arch image index
- 17:14Runtime platform selection
- 19:48Platform variants explained
- 20:08Multi-OS manifests in registries
- 21:35Building multi-arch images
- 22:20Demo: Exploring image blobs
- 24:06Q&A session
related talks
34mDeep Dive: Cloud Native Buildpacks
10mLightning Talk: OCI Images for More Than Containers, Jon Johnson, Google
35mIntro: Cloud Native Buildpacks
36mIt’s Complicated: Relationships Between Objects In OCI Registries
36mModifying the Immutable: Attaching Artifacts to OCI Images
38mCloud Native Buildpacks: A Paradigm Shift for Enterprise App Builds
23mRendered Manifests and OCI
49mContainerd Fundamentals