feat(docker): OpenClaw agent fleet compose + real configs (MS22-P1a)
All checks were successful
ci/woodpecker/push/infra Pipeline was successful

This commit is contained in:
2026-03-01 07:54:03 -06:00
parent 512a29a240
commit 256171cc62
11 changed files with 474 additions and 0 deletions

View File

@@ -0,0 +1,47 @@
# OpenClaw Agent Instance Setup
Each service in the OpenClaw fleet reads:
- A per-agent environment file: `docker/openclaw-instances/<agent>.env`
- A per-agent JSON5 config: `docker/openclaw-instances/<agent>.json`
## 1. Fill in API keys in `.env` files
Set `ZAI_API_KEY` in each instance env file:
- `jarvis-main.env`
- `jarvis-projects.env`
- `jarvis-research.env`
- `jarvis-operations.env`
## 2. Generate unique gateway tokens per agent
Generate one token per instance:
```bash
openssl rand -hex 32
```
Set a different `OPENCLAW_GATEWAY_TOKEN` in each `.env` file.
## 3. Deploy the Docker Swarm stack
From repository root:
```bash
docker stack deploy -c docker/openclaw-compose.yml jarvis
```
## 4. First-time auth (if needed)
If an instance requires first-time login, exec into the running container and run:
```bash
openclaw auth
```
This uses OpenClaw's headless OAuth device-code flow.
## 5. Use Mosaic WebUI terminal for auth
You can complete the device-code auth flow from the Mosaic WebUI terminal (xterm.js) attached to the service container.