Docker / TUIReleased

dtop

dtop starts from a concrete need: open one tool, understand the state of a Docker Engine, and take the next action without rebuilding context from scattered commands.

Tell us what you want to observe

01 /

When Docker's state is scattered

A Docker environment is more than a list of containers. CPU and memory usage, health, Compose stacks, images, networks, volumes, and available updates all matter before an operator changes anything.

The CLI remains the source of truth, but a quick review can require several separate queries. dtop addresses that first moment: understand what is happening and where an intervention makes sense.

02 /

A console for looking and acting

The application opens on containers and lets users switch between Containers, Stacks, Images, Networks, and Volumes with the keyboard. From there they can inspect details, follow logs, open a shell, refresh state, or act on one or several resources.

The goal is not to hide Docker behind a magic layer. It is to bring context and common actions into a compact view so the operator can reach a decision faster.

03 /

Operate with clear signals

Image updates appear as states that explain what remains: pull, recreate, or verify. Destructive actions require confirmation, and remote operations require SSH or mutual TLS; plaintext TCP connections are rejected.

That makes dtop an operational surface for a local or verified remote Engine, without its own daemon or web service and without taking the Docker CLI's place.

04 / getting started

How to install dtop

The stable release includes a versioned installer for Linux and macOS. It detects the platform, verifies the package, and lets you install it for your user or system-wide.

Quick installation

With curl

curl -fsSL https://github.com/ricardoqsx/cktop/releases/download/dtop-v0.5.0/install-dtop.sh | sh

With wget

wget -qO- https://github.com/ricardoqsx/cktop/releases/download/dtop-v0.5.0/install-dtop.sh | sh

Verify the installation

dtop --version

05 / next step

Do you have an operational tool to build?

Tell us what information you need to bring together, which decisions repeat, and where friction appears. We can explore whether a focused utility makes sense.

Explore a similar need