Hysen Labslazydocker
The lazier way to manage everything docker
Lazydocker: the lazier way to run Docker from a terminal
A minor rant starts the README about docker-compose ps, restarting a service, and losing the log stream. Lazydocker is the answer it proposes: a terminal UI that puts the whole environment and common commands in one place.
The problem it's solving
The elevator pitch walks through a familiar loop. A service is down, docker-compose ps shows which one, a restart does not help, and the log stream is cluttered by other services. Following one service's logs dies whenever the service dies, and running a service in its own window wastes a terminal. Memorizing docker commands is hard, memorizing aliases is slightly less hard, and tracking containers across multiple terminal windows is nearly impossible. The proposed answer is everything in one window with every common command one keypress away, plus the ability to add custom commands.
What you can actually do?
The feature list is practical. You can view the state of the docker or docker-compose environment at a glance, view logs for a container or service, and see ASCII graphs of container metrics that you can customize to measure nearly any metric. You can attach to a container or service, restart, remove, or rebuild them, view the ancestor layers of a given image, and prune containers, images, or volumes that are hogging disk space.
Installation and the fine print
Installation has several paths. The Homebrew formula lives in core, but the README suggests tapping the project formula for more frequent updates, and it works on Linux too. A binary release script installs to $HOME/.local/bin by default, configurable with a DIR environment variable, and a Docker method mounts a config path and suggests an alias. The FAQ covers real quirks: logs are only shown from the last hour by default to limit machine load, and running lazydocker in a Docker container is a known bug where logs and CPU usage are not visible. Maintenance is funded by contributors and sponsors, whose avatars or logos can appear in the project, and special thanks go to Warp and Tuple.
Editorial conclusion
The tool is a Go terminal UI built on gocui, but the README sells it on workflow: less typing, fewer windows, and the whole container state visible at a glance.
Community notes