Docker Commander

August 7, 2026 · View on GitHub

A guide to each part of the app. Most pages map 1:1 to a menu item; the last two cover installation and configuration.

New here? Start with Getting started.

Project home page: docker-commander.app.

Compute

  • Dashboard — host overview, disk usage, running containers
  • Containers — create/run, lifecycle, console, files, logs, processes
  • Stacks — Compose stacks: discover, lifecycle, view / edit & redeploy the compose file on its host
  • Projects — managed Compose folders: edit + live validation, deploy, profiles, templates, import/export
  • Templates — reusable presets, builder service blocks, and shared definitions (built-in + your own)
  • Images — pull, build, push, tag, save/load/import, history, prune
  • Volumes — list, inspect, create, remove, prune, browse files

Network

  • Networks & Topology — manage networks (create/connect/disconnect/prune) and the connectivity graph

Observability

  • Logs — aggregated streaming, regex search, structured parse rules
  • Events — the live Docker event feed
  • Alerts — rules, conditions with a lifetime, the feed, delivery records, webhooks, email, Prometheus

System & administration

  • Hosts — local / TCP+TLS / SSH daemons, host-key trust, per-host email
  • Registries — stored credentials for private pull & push
  • Users & roles — accounts, permissions, read-only
  • Your profile — your own account, second factors, sessions, and what you can reach
  • Settings — feature flags, localhost 2FA, MCP token lifetimes, LDAP, SMTP
  • Audit log — record of privileged actions
  • MCP (AI tools) — remote control from AI tools (Claude Code/Desktop, Cursor): tokens, OAuth, the safe tool surface

Operations

  • Getting started — first run, 2FA, the basics
  • Deployment — running on a server (systemd, HTTPS, config, logs, health, self-update)
  • How it's tested — the test tiers, incl. real multi-daemon runs over TCP/SSH, and what isn't covered
  • Limits — every cap you can actually hit, and which are adjustable
  • Gotchas — behaviours of this codebase that cost real debugging time once
  • Dev environment — local setup, and the throwaway services the tests expect
  • Changelog — what changed in each release

Screenshots used throughout live in docs/images/.