Docker Deployment (A1)

Enterprise plan §33.2 Phase A1 / §33.3 item 2. docker compose up should put a pilot online in under five minutes — the first buyer conversation happens in a browser, not a terminal.

Image facts

Multi-arch: linux/amd64 + linux/arm64 (matches the release workflow).
The embedding model (minishlab/potion-retrieval-32M, ~124 MB) is baked into the image at build time (HF_HOME=/opt/brain-model), so the container boots offline — no HuggingFace call at first start. This is the enterprise/air-gapped posture; the pinned revision (HF_COMMIT build arg) makes the bake reproducible.
Runtime: debian:bookworm-slim, non-root user brain (uid 1000), read_only rootfs + tmpfs, cap_drop: ALL, no-new-privileges.
Healthcheck: curl /health (the endpoint is always auth-exempt by design).
Loopback-safe default preserved: BIND_HOST=127.0.0.1; a 0.0.0.0 bind without BIND_PUBLIC logs a loud warning (the opt-in is env presence), and any non-loopback bind without auth refuses to start — the run/compose examples below set both BIND_PUBLIC=1 and a token.

Build

docker build -t brain-server:local .
# change the pinned model revision if you ever need to:
docker build --build-arg HF_COMMIT=<revision> -t brain-server:local .

Run (single container)

docker run -d --name brain-server \
  -p 127.0.0.1:8765:8765 \
  -v "$PWD/data:/data" \
  -e BIND_HOST=0.0.0.0 -e BIND_PUBLIC=1 \
  -e AUTH_TOKEN=<token> \
  brain-server:local

State lives under /data in the container:

Path	Purpose
`/data/brain.db`	SQLite store (`BRAIN_DB_PATH`)
`/data/keys/`	JWT signing/verification PEMs (`BRAIN_JWT_KEY_DIR`) and the UMP operator Ed25519 key (`BRAIN_UMP_KEY_DIR`) — the image and compose point both key dirs at the same `/data/keys` volume
`/data/auth-token`	opaque bearer token file (0600)

Compose (recommended)

docker compose up -d                      # API-first pilot, loopback only
docker compose --profile sso up -d        # + OAuth2-Proxy SSO edge

See docker-compose.yml for the full service definition and docs/proxy-sso.md for the SSO profile.

The Dioxus GUI is not built into the image (it is a separate crate served from client/dist). The SvelteKit + Tauri shell (shell/) is a separate frontend that can serve the same /app seat once built for that base path. To serve the UI from the container, build the bundle (client/deploy-web.sh) and mount it:

    volumes:
      - ./client/dist:/app/client/dist:ro
    environment:
      BRAIN_CLIENT_DIST: /app/client/dist

Backup / restore

The brain CLI is in the image:

docker exec brain-server brain backup /data/backup-$(date +%F).bin
# restore (with the server stopped):
docker stop brain-server
docker run --rm -v "$PWD/data:/data" brain-server:local \
  brain restore /data/backup-YYYY-MM-DD.bin --passphrase-file /data/pass
docker start brain-server

Snapshot retention is a compile-time constant (SNAPSHOT_KEEP = 4 in src/integrity.rs) — the last four verified copies are kept, older ones pruned. An operator-tunable BRAIN_BACKUP_RETENTION env var is not implemented (the old v1.19 A5 note overstated it); edit the constant if you need a different window.

Publishing (A1 follow-up)

Image publish to GHCR/Docker Hub (markfietje/brain-server) is the remaining distribution step — the Dockerfile and compose land first; publish is a workflow + credentials item (see report Round 27).

Brain Server