Docker Sandbox

**Quick judgement**: This skill is a robust, well-thought-out Docker Desktop–based sandboxing layer for agents and arbitrary code. It’s particularly valuable when security and isolation matter more than raw performance or deployment flexibility. **Strengths & benefits** - Per-sandbox VM isolation significantly reduces risk from untrusted or destructive code. - Detailed, practical CLI interface for lifecycle management (create/run/exec/stop/rm/reset/save). - Fine-grained outbound network controls (allow/block hosts and CIDRs, proxy policies, logging) enable strong egress restrictions. - Good ergonomics for real workflows: persistent dev sandboxes, templates, and clear workspace mounting semantics across OSes. - Explicit patterns for safe package exploration, locked-down agent runs, and persistent environments. **Key risks / limitations** - Requires Docker Desktop 4.49+ and the sandbox plugin, limiting compatibility to supported environments (no pure server/docker-engine setups). - Some edge cases (e.g., Node.js `fetch` ignoring proxy env vars) can lead to unexpected network behavior unless the documented workarounds are applied. - Complexity of Docker + VM + proxy setup may introduce operational friction and potential misconfiguration, especially on Windows (path conversion issues) and after Docker updates. **Recommended scenarios** - Use when running untrusted packages or third-party code, especially on developer machines or CI where host safety is critical. - Use for security-focused agent workloads that need strict outbound network policies and reproducible environments. - Use to test destructive or experimental operations in a controlled, resettable environment. - Consider alternatives or simpler setups if you only need basic containerization, lack Docker Desktop support, or operate exclusively on headless Linux servers without the sandbox plugin.