Building a Docker Backend for Garden
summary
A Docker backend for Garden is implemented that starts a Garden-style init process inside Docker containers, uses the Docker daemon to pull images and spawn containers, and integrates with lattice (vagrant demo) so garden CLI and docker ps both list the same containers. The prototype reuses existing Go libraries, boots containers fast and shows successful health checks, but lacks user namespaces and snapshot/restore support so multi-tenant isolation and daemon upgrades are unresolved trade-offs. The claim is practical: it works end-to-end, exposes Docker tooling, and surfaces the exact feature gaps to close.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:27Agenda
- 1:54Containers
- 2:10What are containers
- 4:18garvin
- 6:52Docker vs Garden
- 7:40Use cases coming together
- 8:07What is Garden
- 9:58What is Docker
- 10:54Docker for local development
- 11:39Whats great about Garden
- 12:45Whats not great about Garden
- 13:49Community
- 14:21Why Docker
- 14:51Not so great
- 16:08Building a Docker Backend for Garden
- 16:26Docker Community
- 16:57Goals
- 18:01How it works
- 25:22What Doesnt Work
- 26:09Is This a Good Idea
- 26:50Use Cases
- 27:42QA
- 30:28Wrapup