From `docker push` to Bytes on Disk: Inside Distribution
summary
DigitalOcean describes how its Container Registry uses CNCF Distribution codebase and implements the OCI Distribution API so a push becomes bytes on disk via repository-scoped blobs, manifests and tags. Clients check blobs with HEAD, optionally blob-mount to avoid uploads, then do POST/PATCH/PUT chunked uploads; Docker commonly sends a single huge PATCH (so expect 10+ GB bodies). Back end is an S3-compatible store with S3 multipart uploads, and safe garbage collection requires switching the registry to read‑only and token expiry coordination.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:11Container registries
- 14:12Docker pull
- 15:50Internals
- 19:20Bytes on Disk
- 25:15Garbage Collection
- 28:38Wrap Up
- 29:23Questions
related talks
28mRegistries After Dark
08mYou Can Store That in a Container Registry?!
28mThe ABC of Container-Image Management
36mContainer Registries, No Longer Just for Containers!
30mDIY Private Container Registry
31mKubernetes at DigitalOcean: Building a Platform for the Future
15mKeynote: Best Practices In Implementing Container Image Promotion Pipelines
21mWhy we built Docker