Repository navigation
Architecture
One Debian container provides one interactive Claude Code environment. Docker Compose owns runtime configuration. There is no HTTP service, orchestration layer or hosted control plane.
| Question | Canonical explanation |
|---|---|
| How is Claude installed, and what does health mean? | Image/process model |
| Which Compose files are optional? | Base and overlays |
| Which files survive recreation? | Storage and identity |
| What is the runtime user and SSH privilege difference? | Identity/capability model |
| How do login, expiry and revocation affect persisted state? | Authentication lifecycle |
| Where are filesystem/network trust boundaries? | Boundaries |
| Why were these choices made? | Architecture decisions |
The base runs UID/GID 1000 and publishes no ports. SSH explicitly adds a root daemon while keeping dev login shells; its own host-key volume persists server identity. Vault access is absent by default and read-only when that overlay is selected. Mem remains user-local and optional.
Preserving home files does not guarantee provider authorization remains valid. Read-only mounts do not prevent data disclosure. Use Security for the consequences and Maintenance for updates/recovery.
Procedures live in the reviewed canonical repository guides. Wiki pages provide navigation and do not add runtime capabilities. Security reporting · Roadmap