Skip to content

User manual · v1.7.2

One page per part of the app, grouped roughly like the sidebar. The last section covers installing and running it.

New here? Start with Getting started.

Project home page: docker-commander.app.

  • Dashboard — host overview, disk usage, running containers
  • Containers — run, start/stop, console, files, logs, processes
  • Stacks — Compose stacks: lifecycle, view and edit the compose file, redeploy
  • Projects — managed Compose folders: edit, validate, deploy, profiles, import/export
  • Templates — reusable presets, builder blocks and shared definitions, built-in and your own
  • Images — pull, build, push, tag, save/load/import, history, prune
  • Volumes — create, inspect, remove, prune, browse files
  • Backup jobs — run your own backup command against volumes
  • Resources — CPU, memory and network per container and stack, top talkers, disk usage
  • Logs — live logs from many containers, regex search, parse rules
  • Events — the live Docker event feed
  • Alerts — rules and conditions, the feed, delivery records, webhooks, email, Prometheus
  • Hosts — local, TCP+TLS and SSH daemons, host-key trust, per-host email
  • Registries — credentials for private pull and push
  • Users & roles — accounts, permissions, read-only
  • Your profile — your account, second factors, sessions, what you can reach
  • Settings — feature flags, localhost 2FA, MCP tokens, LDAP, SMTP, data retention; also hosts the two pages below
  • Policy rules — checks on project deploys (off / warn / block)
  • Recovery bundle — export and import your setup
  • Audit log — record of privileged actions
  • Troubleshooting — health checks for the host’s Docker setup
  • MCP (AI tools) — control from AI tools (Claude Code/Desktop, Cursor): tokens, OAuth, allowed tools
  • Getting started — first run, 2FA, the basics
  • Installing — binaries, Homebrew, packages, Docker, from source; verifying a download; running as a service
  • Configuration — every flag and environment variable
  • Docker versions — which Engine and Compose versions are tested
  • Security model — how access to the daemons is protected
  • Architecture — how the pieces fit (for developers)
  • Deployment — running on a server: systemd, HTTPS, config, logs, health, self-update
  • Limits — every cap you can hit, and which can be changed
  • How it’s tested — test tiers, multi-daemon runs over TCP/SSH, what isn’t covered (for developers)
  • Gotchas — pitfalls in this codebase that cost real debugging time (for developers)
  • Dev environment — local setup and the services the tests expect (for developers)
  • Changelog — what changed in each release

Screenshots live in docs/images/.