The Wayback Machine - https://web.archive.org/web/20260406221205/https://docs.docker.com/ai/sandboxes/
Share feedback
Answers are generated based on the documentation.

Docker Sandboxes

Availability: Experimental

Docker Sandboxes run AI coding agents in isolated microVM sandboxes. Each sandbox gets its own Docker daemon, filesystem, and network β€” the agent can build containers, install packages, and modify files without touching your host system.

Get started

Install the sbx CLI and sign in:

$ brew install docker/tap/sbx
$ sbx login
> winget install -h Docker.sbx
> sbx login

Then launch an agent in a sandbox:

$ cd ~/my-project
$ sbx run claude

See the get started guide for a full walkthrough, or jump to the usage guide for common patterns.

Learn more

  • Agents β€” supported agents and per-agent configuration
  • Custom environments β€” build reusable sandbox images with pre-installed tools
  • Architecture β€” microVM isolation, workspace mounting, networking
  • Security β€” isolation model, credential handling, network policies, workspace trust
  • CLI reference β€” full list of sbx commands and options
  • Troubleshooting β€” common issues and fixes
  • FAQ β€” login requirements, telemetry, etc

Feedback

Docker Sandboxes is experimental and under active development. Your feedback shapes what gets built next. If you run into a bug, hit a missing feature, or have a suggestion, open an issue at github.com/docker/sbx-releases/issues.

Docker Desktop integration

Docker Desktop also includes a built-in sandbox command (docker sandbox) with a subset of features. The sbx CLI is recommended for most use cases.