dockza
v0.4.0 · MIT · Node 24+
Docker at terminal speed.
A lightweight TUI for Docker. Watch and control your Compose stacks, follow logs, see what uses what, and clean up what's left behind — without leaving the terminal.
npm install -g dockza.app
Stacks — containers grouped by Compose project, with live counts per stack. The orange ↑ marks a container running an outdated image.
Five views, one keystroke apart.
Press 1–5 to jump, Tab to cycle, / to filter any list as you type, Enter to open whatever row you're on. The rail stays put and keeps a live list of your stacks — click one to jump straight into it.
- 1◰StacksCompose projects as a collapsible tree, with running / errored / stopped counts per project.
- 2◧ContainersEvery container, flat: status and uptime, network, live CPU and memory, published ports.
- 3◩ImagesRepository, tag, ID, age, size — and USED BY: the containers created from each one.
- 4◪VolumesDriver, mountpoint, size and USED BY. Leftovers are marked orphaned or dangling.
- 5◫NetworksDriver, scope, ID, age, and USED BY: every container attached, running or stopped.
Everything links.
Enter opens a detail panel for any container, image, volume, network or stack. A container's shows its image and stack, each published port with a URL, its address and DNS names on every network, its mounts, the containers it depends on, and its environment.
Tab moves between sections, Enter follows a link to the thing it names, and [ / ] walk back and forward through where you've been.
Stop a whole stack — or take it down.
On a stack header, s, S, r and k stop, start, restart or kill every service in it — dependencies start first and stop last, as compose does.
Stop asks how far to go: y only stops, d takes the stack down like docker compose down, v adds -v. Networks and volumes another container still uses are kept. It all goes through the Docker API, so it works against a remote daemon too.
Clean up without the guesswork.
USED BY names the containers holding on to each image, volume and network. A volume left behind by a removed compose project reads ○ orphaned; an anonymous one nothing mounts reads ○ dangling.
Mark rows with Space — or a for every row shown — and d deletes them together. D clears out a whole kind of volume at once, with the count and the space it frees shown first. Anything in use is skipped, and the built-in bridge, host and none networks are never touched.
Logs that keep up.
l streams a container's log straight into the pane, with stderr in orange. f toggles follow, g and G jump to top and bottom, and a 5,000-line scrollback cap keeps a chatty container from running away with your memory. Enter opens the container's detail; [ brings you back.
Small things that add up.
Filter as you type
Every list narrows with each key, and matches past the name: image, ID, any tag, compose project.
Copy what you need
A name, an ID, a port's URL, a -p or -v spec, NAME=value. System clipboard — or OSC 52 over SSH.
Back and forward
Step through the screens you visited, followed links included, landing on the row you left.
Environment, in full
Browse a container's variables and expand any value — long or multi-line — to read it whole.
Shell in
Opens your platform's own terminal with docker exec into the selected container.
Outdated images
Flags a container whose image tag now points at a newer local image; the image's detail says what superseded it.
Every key, on one card.
Press h anywhere in the app for the full reference, without leaving what you were doing.
Navigation
Containers & stacks
Detail panel
Images, volumes, networks
Log viewer
Dialogs
Talks to whatever daemon you have.
dockza finds the socket on its own. When it shouldn't, DOCKER_HOST decides — rootless Docker, podman, a named pipe, or a daemon on another machine.