> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zap.wzrd.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Docker

> Local container sandboxes for development: same contract, container isolation, no cloud account required.

<img src="https://mintcdn.com/gratitude5dee-zap-56/Y4G9H4edehsua_Ul/images/logos/docker.svg?fit=max&auto=format&n=Y4G9H4edehsua_Ul&q=85&s=69a270ae4c2259b6657d5df94acbec07" alt="Docker" style={{ height: "32px", width: "auto" }} noZoom width="24" height="24" data-path="images/logos/docker.svg" />

The Docker adapter runs Zap runtimes as local containers. Use it for development when you don't want a cloud sandbox account.

```bash theme={null}
zap compose --weight light --sandbox docker --dry-run --json
zap runtime up --json
```

* Isolation: `container` — weaker than a VM or microVM. Prefer Box or a microVM provider for untrusted workloads.
* Containers start from the runtime profile image; the runtime injects only the per-runtime env allowlist (`TENANT_ID`, `RUNTIME_ID`, `RUNTIME_TOKEN`, `GATEWAY_URL`, `GATEWAY_TOKEN`, `ZAP_ENVIRONMENT`) — never your host environment.
* Filesystem work is rooted at `/zap/fs` inside the container; `sandbox.exec` runs argv commands, not shell strings.
* Requires a local Docker daemon; `zap doctor --json` reports whether it is reachable.

## Capabilities

| capability               | value       |
| ------------------------ | ----------- |
| isolation                | `container` |
| stop                     | yes         |
| snapshot / fork / resume | no          |
| ports                    | no          |
| max command seconds      | 3600        |