Extending Docker for using web3/decentralized storage
summary
Goal is to make docker push/pull use a decentralized storage backend instead of a central registry. Attempts cover containerd grpc extension (upstream draft, not merged), a working containerd client push prototype that requires a custom library and isn’t the same containerd instance Docker uses, hacking the Docker daemon (too invasive), and a successful pattern: run a local registry with alternative backend (distribution drivers) and a Docker Desktop extension that starts that registry and handles credentials; client-side encryption and an uplink CLI are used.
AI-written summary · about
chapters (10)
- 0:00Extending Docker with web3 storage
- 3:56Container d plugin extensions
- 6:01Custom push/pull API
- 10:20Docker storage limitations
- 12:08Modifying Docker daemon
- 13:34Decentralized storage registry
- 15:39Local registry with decentralized backend
- 17:29Docker Desktop extensions
- 19:16S3-compatible storage approach
- 20:20Summary and future integration
related talks
30mProject Decker: Cloud Foundry with Docker
05mWhat are Docker Extensions
29mIntroduction and Deep Dive Into Containerd
21mcontainerd: Project Update and Deep Dive
06mIntroduction to Containerd
35mA Containerd And Friends Update: What’s New In Runtimes?
37mProject Update and Deep Dive: Containerd
01h 35mDocker Deep Dive for JavaScript Developers