Why Empty Sandboxes Break Developer Experience | Docker

This post introduces and details Docker Sandbox 'kits' as a solution to the developer experience challenges posed by empty, isolated sandboxes. It explains how kits, defined by a `spec.yaml` and optional files, allow for the repeatable installation of tools (e.g., SDKs, CLIs), configuration of network access (allowed/denied domains, service domains), and secure credential management (proxy-managed secrets). The post differentiates between `sandbox` kits (for building agents) and `mixin` kits (for extending existing sandboxes), advocating for the latter's composability. It highlights the benefits of kits for sharing setup configurations within teams and across organizations via OCI artifacts, ultimately making sandboxes more survivable as development tools by providing a convenient and configurable environment.