dockctl is a keyboard-driven terminal UI for Docker and Podman. Containers, images, volumes, networks and Compose stacks, all one keystroke away. Written in Rust, so it starts instantly and stays out of your way.

~ dockctl --runtime docker

        

Playing a demo. Click the terminal to take the wheel.

Two ways to look at the same fleet.

Themes in dockctl aren't color schemes. Each one owns its own keys, layout and views, so you choose how you like to work. Switch with one line of config, or try both in the terminal above.

The default. Full-width tables, a vim-style :command line with autocomplete, inline describe and log views, sorting, regex filtering and wide mode.
Panels side by side: alerts, resources and status on the left, with an accordion of containers, images, volumes and networks on the right. Jump between panels with 1–7.
# ~/.config/dockctl/config.toml
[general]
default_runtime = "auto"
refresh_interval_ms = 1000
theme = "operator"

[columns]
containers = ["Name", "State", "Ports",
              "CPU", "Memory", "Status"]

Everything is a keystroke away.

See

  • Live CPU, memory and network I/O for every container
  • Host CPU, RAM and swap next to Docker's own totals
  • Alerts for dangling images, unused volumes and stopped containers
  • :statusA system pulse view

Find

  • :Command mode with ghost-text autocomplete
  • /Regex filter across any resource
  • ⇧OSort by any column, or ⇧N ⇧S ⇧A for name, state or age
  • ⌃WWide mode for the extra columns
  • Columns you can add, drop and reorder in TOML

Act

  • srxStop, restart or remove a container
  • lFollow its logs inline
  • dDescribe anything without leaving the table
  • EExec into it in a tmux split pane
  • :composeBring stacks up, down or restart them

Docker and Podman sit behind one runtime trait. dockctl finds whichever socket is running, or you can pick one with --runtime.

Follow a keypress.

The engine provides hooks. The theme does everything else. A theme reads your keys, decides what they mean and hands the engine a typed action. The engine runs it against your runtime, and the next tick redraws the screen.

That split is why a new theme is a single trait to implement:

pub trait Theme: Send + Sync {
    fn name(&self) -> &str;
    fn draw(&self, frame: &mut Frame,
            app: &App, config: &DockctlConfig);
    fn handle_key(&self, key: KeyEvent,
            app: &mut App, config: &DockctlConfig)
        -> ThemeAction;
}
  1. You press son the selected container
  2. Themehandle_key() returns StopContainer { id }
  3. Enginethe event loop runs the action asynchronously
  4. Service hooksContainerService stops it
  5. Runtime traitDocker through bollard, Podman through bollard and its CLI
  6. Your socket/var/run/docker.sock or the Podman socket
  7. Next tickfresh state comes back up and theme.draw() repaints

Install it.

One static binary, no daemon of its own. Download it for your platform, or build it from source with Cargo (Rust 1.85 or newer).


        
      

Run it

# finds Docker or Podman on its own
dockctl
dockctl --runtime podman

You'll need

Docker or Podman running, a terminal with 256 colors, and macOS or Linux. Windows under WSL2 hasn't been tested yet.