cruise: Manage Docker Containers in a Terminal UI

Overview

Cruise is a keyboard-first terminal interface for working with Docker. It brings container, image, volume, and network management into an interactive client, addressing the repetition and verbosity of handling these tasks through commands alone.

It is aimed at terminal-oriented developers who want both management controls and monitoring in one place. The repository description explicitly says this is not the main repository, so check the project’s homepage for the canonical project location.

Key Features

• Manage lifecycles of Docker containers, images, volumes, and networks.
• View monitoring information through a centralized interface.
• Scan images for vulnerabilities using Trivy or Grype, as described in the README.
• Inspect Docker artifacts in detail.
• Interact through a keyboard-first TUI built with Go and Bubbletea.

Use Cases

• Developers who frequently start, stop, or inspect containers and prefer interactive controls to repeated CLI commands.
• Operators who want a terminal-based view for checking Docker artifacts and monitoring activity.
• Teams or individuals reviewing container images for vulnerabilities as part of local development workflows.

Getting Started

After installing Cruise, run:

cruise

See the installation documentation for setup details and the repository README for project information.

Alternatives

• ctop: ctop focuses on live container metrics and inspection, while cruise also provides lifecycle controls and image vulnerability scanning.

Considerations

• The README says the current implementation supports Docker only. Support for other containerization tools and Docker Compose is presented as future work.
• Using the client requires Docker to be available for the artifacts it manages. Image scanning is listed as a feature, but setup details are not provided in the supplied README excerpt.
• This repository is explicitly described as not being the main repo. Confirm the canonical project location before depending on it.
• The input metadata lists Apache-2.0, while the README states MIT. Check the repository’s license file to resolve this discrepancy before relying on a particular license.