Server sandboxes
See and manage a server's Docker engine, agent images, containers and Cloudflare workspaces from the Sandboxes screen.
The Sandboxes screen lists each connected server below this Mac, with the same cards: Docker engine, agent images, containers, and Cloudflare. Sign in to a server (in the sidebar) to see its sandboxes.
The cards#
| Card | Shows | Actions |
|---|---|---|
| Docker | Whether the server's engine is running, its version and the number of running containers | |
| Agent Image | harness-agent:latest and harness-agent-browser:latest: present or not, size, when built | Build (admin). Build progress appears on the card. |
| Containers | Only the containers this server started (its instance label), with CPU and memory | Logs (operator, redacted), stop and remove (operator) |
| Cloudflare | The bridge URL, whether the token is set, bridge health, relay status, the server's Cloudflare projects and running agents | |
| Workspaces in Cloudflare | Kept Cloudflare workspaces of the server's projects | Save branch and destroy (admin) |
Other workloads on the server's Docker are never listed or touched.
Only one image build runs at a time; a second request gets 409 building. Building needs Docker running on the server (409 docker_unavailable otherwise). Docker is asked at most every few seconds however many clients are watching, and the bridge's health every 15 seconds.
Build the images on a new server#
- Sign in as an admin
Select the server in the sidebar and sign in.
- Build the agent image
On Sandboxes, under the server, press Build on the Agent Image card.
- Build the browser image
If projects use browser testing, build
harness-agent-browser:latesttoo.