ctop: Monitor Container Metrics in a Terminal

Overview

ctop is a top-like command-line interface for monitoring container metrics. It condenses information about multiple containers into a live terminal view and also provides a single-container view for closer inspection.

It is useful when you need a quick read on container activity from a shell, especially while working with Docker or runC. The project supports those runtimes directly; connectors for other container and cluster systems are described as planned.

Key Features

• Shows real-time metrics for multiple containers in a compact terminal interface.
• Opens a single-container view for detailed inspection.
• Supports Docker and runC connectors.
• Filters the displayed containers and sorts them by a selected field.
• Toggles between active containers and all containers, including non-running ones.
• Provides container logs and an option to open an exec shell.
• Saves filters, sort field, and other settings to a configuration file.
• Offers packages or installation options for Linux, macOS, and Windows, as well as a Docker image.

Use Cases

• Developers can check container health and activity during local development without leaving the terminal.
• Operators can scan multiple containers during troubleshooting and filter down to a specific workload.
• Teams running Docker or runC can inspect logs or open a shell for an individual container from the interface.
• Terminal-focused users can monitor containers over a remote shell or in environments where a browser dashboard is inconvenient.

Project Facts

• Language: Go
• License: MIT
• Stars: 17.8k
• Forks: 589
• Topics: command-line, commandline, containers, docker, monitoring, runc, top
• Archived: No

Getting Started

Install through Homebrew on macOS:

brew install ctop

Then run ctop. It uses Docker host variables by default. See the README for other installation methods, options, and connector configuration.

Considerations

• Built-in connector support is for Docker and runC. Support for other container and cluster systems is not presented as available.
• The interface is terminal-based, so it is best suited to users comfortable working in a command line.
• Container access depends on the runtime connection being available to ctop. The Docker example mounts the Docker socket read-only.
• Installation methods and package maintenance vary by platform. The README identifies the Debian/Ubuntu package as third-party maintained.