openclaw docker deploy
OpenClaw Docker deployment with compose baseline
A reproducible container deployment path for openclaw local and docker intent.
1. Why Docker
It standardizes runtime, improves collaboration, and simplifies rollback.
- Unified dependency graph
- Fast rollback
- CI/CD friendly
2. Compose baseline
Official compose layout uses `openclaw-gateway` and `openclaw-cli`.
Official compose core snippet (trimmed)
services:\n openclaw-gateway:\n image: ${OPENCLAW_IMAGE:-openclaw:local}\n ports:\n - \"${OPENCLAW_GATEWAY_PORT:-18789}:18789\"\n openclaw-cli:\n image: ${OPENCLAW_IMAGE:-openclaw:local}\n network_mode: \"service:openclaw-gateway\"- Gateway default port is 18789
- Image is controlled by `OPENCLAW_IMAGE`
- CLI uses `network_mode: service:openclaw-gateway`
3. Post-deploy checks
Confirm gateway health before running business workflows.
- Check `http://127.0.0.1:18789/healthz`
- Run `docker compose run --rm openclaw-cli dashboard --no-open`
- Inspect gateway logs for auth/pairing errors
Frequently asked questions
Docker or native deployment?
Docker is usually better for teams and production; native is fine for quick tests.
Can containers access web search features?
Yes, with correct networking policy and outbound proxy allowlists.