Terminal dashboard for Docker monitoring across multiple hosts with Dozzle integration.
Terminal dashboard for Docker monitoring across multiple hosts with Dozzle integration.
A terminal based dashboard for Docker that monitors multiple hosts in real-time.
dtop provides a comprehensive summary of all Docker containers running on your system, displayed directly in your terminal. Get instant visibility into container status, resource usage, and key metrics without leaving the command line. It supports ssh, tcp and local connections and integrates with Dozzle for container logs.
DOCKER_CERT_PATHdtop can be installed through multiple package managers or by downloading the binary directly.
Install using Homebrew for macOS or Linux (recommended):
brew install dtop[!NOTE] Homebrew is recommended as
dtopis in active development with frequent updates. Using Homebrew will automatically upgradedtop.
dtop is released as a docker image. You can pull it from Github.
docker run -v /var/run/docker.sock:/var/run/docker.sock -it ghcr.io/amir20/dtopCurrently, the image is available for amd64 and arm64 architectures.
Downloads the latest release from GitHub.
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/amir20/dtop/releases/latest/download/dtop-installer.sh | shRun directly without installing:
nix run github:amir20/dtopOr install to your profile:
nix profile install github:amir20/dtopFor NixOS or home-manager, add to your configuration:
# In your flake inputs
inputs.dtop.url = "github:amir20/dtop";
# Then use
inputs.dtop.packages.${system}.defaultdtop is written in Rust can be installed using Cargo.
cargo install dtopdtop includes a built-in self-update feature to easily upgrade to the latest version:
dtop updateThis command will:
[!Note] The self-update feature is only available in binaries installed via the install script or downloaded from GitHub releases. Docker images should be updated by pulling the latest image, and cargo installations should use
cargo install dtop --force.
By default, dtop will connect to the local Docker daemon using /var/run/docker.sock. DOCKER_HOST is also supported to connect to other hosts.
…dtop supports command line flags or configuration file. The configuration file reads from the following locations (in priority order):
./config.yaml or ./config.yml./.dtop.yaml or ./.dtop.yml~/.config/dtop/config.yaml or ~/.config/dtop/config.yml~/.dtop.yaml or ~/.dtop.yml[!Note] Both
yamlandymlfiles are supported.
Here's an example configuration:
# Monitor production servers with filters and Dozzle integration
hosts:
- host: ssh://user@prod-server1
dozzle: https://dozzle.prod-server1.com/
filter:
- status=running
- label=environment=production
- host: ssh://user@prod-server2
dozzle: https://dozzle.prod-server2.com/
filter:
- status=running
- label=environment=production
# Use Nerd Font icons for better visuals
icons: nerdOr monitor specific application stacks:
# Development environment - only show healthy web services
hosts:
- host: local
filter:
- label=app=web
- status=running
- health=healthySee config.example.yaml for more examples.
dtop supports Nerd Fonts for enhanced icon display. Nerd Fonts are fonts that have been patched to include additional glyphs and icons commonly used in terminal applications.
Once you have a Nerd Font installed and configured in your terminal, enable Nerd Font icons in dtop:
# Via command line
dtop --icons nerd
# Or in config file
icons: nerd[!Note] If icons appear as boxes or question marks, ensure your terminal is using a Nerd Font. The default
unicodemode works with any terminal font.
Monitor containers running on the local Docker daemon using --host local. dtop respects the DOCKER_HOST environment variable. If DOCKER_HOST is not set, it falls back to the default Docker socket location (/var/run/docker.sock on Linux/macOS).
dtop --host local
# or simply
dtopConnect to remote Docker daemons over unencrypted TCP connections. This is useful for development environments but should only be used on trusted networks.
dtop --host tcp://host2:2375[!Warning] TCP connections are unencrypted. Only use on trusted networks or with proper firewall rules.
Connect to remote Docker daemons over encrypted TLS connections. Requires certificates to be configured via the DOCKER_CERT_PATH environment variable.
export DOCKER_CERT_PATH=/path/to/certs # Directory containing key.pem, cert.pem, and ca.pem
dtop --host tls://host2:2376Establish an SSH connection to a remote host and monitor containers running on it. This is the recommended method for secure remote connections.
dtop --host ssh://user@host
# With custom port
dtop --host ssh://user@host:2222You can monitor multiple Docker hosts simultaneously by specifying multiple --host flags:
dtop --host local --host tcp://host2:2375 --host ssh://user@host[!Note] Currently, Dozzle url can only be configured in the configuration file. There is no way to provide it directly in the command line flags.
dtop reads display names and groups directly from Docker labels, with no additional configuration:
dev.dozzle.name → coolify.serviceName → Docker container name.dev.dozzle.group → coolify.projectName → com.docker.compose.project.Empty or whitespace-only labels are skipped. This works even without a Dozzle URL configured, including after container restarts and host reconnections.
I am a big fan of ctop. ctop inspired me to create Dozzle but in the browser. However, it seems like ctop is no longer maintained. I considered forking ctop but deploying with same name would be challenging. I created dtop for my personal use case. I often want to see all my containers at a glance across multiple hosts. dtop achieves that by supporting remote hosts via ssh or tcp. Additionally, since I use Dozzle, I integrated Dozzle into dtop to provide a seamless experience for monitoring container logs.
Contributions are welcome! Please feel free to submit a Pull Request.
MIT License - see LICENSE file for details.
No open issues yet, or sync has not completed.