Features
What do you need Docker to do?
65 capabilities in 8 areas, all in the same binary. Start from the job you have in mind — search for it, or pick one of the questions people usually arrive with.
By area
Or browse the map
Each area has its own page: what it is for, the screens, and the complete list.
- MonitoringLive and historical, per container, per stack and per host.
- Which container is eating the CPU right now?
- What is filling the disk, and what would a prune free?
- Which container is pushing all that traffic?
- Container controlFull lifecycle, not a read-only window.
- Open a shell in a container from the browser
- Restart twelve containers at once
- Upload a file straight into a volume
- Compose & safe deploysPreview, policy, deploy, history, rollback.
- What exactly will this deploy change?
- Has someone changed a container behind compose’s back?
- Roll back to the version from last Tuesday
- AlertingRules with a lifetime, delivered where you look.
- Alert me when a container stays above 80% CPU
- Tell me when a container crash-loops
- Do not page me during Saturday’s maintenance
- Multi-hostAgentless. Local, TCP+TLS or SSH.
- Manage the NAS, two VPS boxes and a laptop from one place
- Let an operator restart containers on staging but not production
- Take a host that sleeps out of monitoring
- Users & accessMulti-user with real boundaries.
- Give a reviewer read-only access
- Sign in with a passkey
- Who stopped that container, and on which host?
- OperationsBoring to run, on purpose.
- Get a Let’s Encrypt certificate without a reverse proxy
- Move the whole setup to a new server
- Back up my volumes with restic on a schedule
- AI tools over MCPOpt-in, and narrower than your own account.
- Ask Claude why a container keeps restarting
- Let an assistant restart a stack but never exec into it
- Revoke the token on one laptop only
How the areas fit together
From noticing a problem to undoing its cause
Monitoring tells you something changed, alerting tells you when it matters, control lets you act — and a deploy can now be previewed, vetoed, recorded and rolled back.
- 01EditValidating Compose editor, secrets kept out of the file.
- 02PreviewEvery service, digest, env and port that would change.
- 03PolicyPrivileged, socket, :latest… off, warn or block.
- 04DeployLocal or remote host, with your registry credentials.
- 05HistoryAn immutable revision with the digests that ran.
- 06RollbackRestore validated in staging, swapped atomically.
Try it on one host tonight
It is one binary and a named volume. If you do not like it, delete both — nothing on your Docker hosts was changed to accommodate it.
docker run -d --name dockercmd \
-p 127.0.0.1:8470:8470 \
--group-add "$(stat -c '%g' /var/run/docker.sock)" \
--read-only --tmpfs /tmp \
--security-opt no-new-privileges \
--cap-drop ALL \
-v /var/run/docker.sock:/var/run/docker.sock \
-v dockercmd-data:/data \
ghcr.io/koduj-dev/docker-commander:latestRead-only root filesystem, no added capabilities, no privilege escalation, bound to localhost. On rootless Docker or Docker Desktop, drop the --group-add line.
Show the minimal command
docker run -d --name dockercmd -p 127.0.0.1:8470:8470 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v dockercmd-data:/data \
ghcr.io/koduj-dev/docker-commander:latestFewer flags, and correspondingly fewer guardrails. Fine for a throwaway look on a machine you do not mind losing; the hardened form above is what belongs on anything you keep.
MIT licensed · no account · no telemetry · Linux, macOS and Windows