Container Registries, No Longer Just for Containers!
summary
Claim: container registries already host non-container artifacts and can be extended safely. Demos show pushing a plain text file and source RPMs as OCI layers, editing manifests to add JSON metadata, and linking images via the new refers API (release candidate in distribution spec). Tools demonstrated: push arbitrary files with oras, inspect and edit manifests with crane, plus regclient/scopio and explorer.ggcr.dev. Result: reuse of content-addressable storage, signatures and SBOM-like metadata stored and retrievable from registries.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:48Container registries in cloud native
- 4:56History of container standards
- 9:11Merkle trees in images
- 13:30New registry use cases
- 17:26Extending with content types
- 20:37Demo: pushing non-container content
- 25:16Editing manifests and metadata
- 27:49Experimenting with features
- 30:12OCI Referrers API
- 31:37Simple and extensible solutions
- 32:39Registry interaction tools
- 34:22Q&A
related talks
08mYou Can Store That in a Container Registry?!
28mRegistries After Dark
30mDIY Private Container Registry
45mImage Layout: Stop Putting Everything in Registries
29mBuilding Signing, Distributing SPDX SBOMs as Artifact Reference Type
44mFrom Containers To Cognitive Agents: Open Source Foundations for Enterprise-Grad...
36mPanel: Native OCI Integration - Leveraging Argo CD Source Content in a Brand New Way
40mNotary v2: Deep Dive and Open Issues