lazydocker is a free terminal app that shows everything Docker is running on one screen. Type lazydocker and you get panels for your Compose project, its services, containers, images and volumes; pick a container and the big panel shows its live logs, CPU and memory graphs, environment and config. Single keys do the rest: r restarts, s stops, d removes, E opens a shell inside the container, and x lists every action for the panel you are in.
It earns its place because it replaces the pile of docker and docker compose commands you would otherwise keep retyping, and the logs follow you as you move between containers. It reads the docker-compose.yml in the folder you start it from, can bring services up and down, has bulk commands for pruning unused images, containers and volumes, and lets you add your own commands in its config file. It comes from Jesse Duffield, who also made lazygit, so the layout and keys feel familiar if you use that.
lazydocker is MIT-licensed and written in Go by Jesse Duffield, who started it in 2019. It has about 53,000 stars and around 90 contributors. The latest release is 0.25.2 from 19 April 2026, and the code still gets updates.
- Repository: github.com/jesseduffield/lazydocker
- Licence: MIT (MIT License)
- Language: Go. Stars: 53.4K. Forks: 1,734. Last push: Nov 15, 2026.
- Scan: safe, Nov 21, 2026, commit 596fd59
Who it is for
Developers who run their apps in Docker or Docker Compose, homelab owners, DevOps engineers and students learning containers. It works on macOS, Linux and Windows from a terminal and needs Docker installed and running.
Getting started
1. Install on macOS or Linux with Homebrew
brew install lazydocker2. Or on Windows, with Scoop
scoop install lazydocker3. Start it, ideally in a folder with a docker-compose.yml. Press x for the actions in each panel and q to quit
lazydocker4. Optional: a short alias, as the README suggests (for bash, use ~/.bashrc)
echo "alias lzd='lazydocker'" >> ~/.zshrcPackage managers install a single program and change nothing else. lazydocker talks to Docker through its socket, so it has the same full control over your containers as the docker command; removing and pruning go through a menu or a confirmation first. Press o in the project panel to open its config file. The README's curl-to-bash option for Linux puts the binary in ~/.local/bin without checking a checksum. Our scan covers the source code, not the prebuilt binaries.
Safety scan
We cloned jesseduffield/lazydocker at commit 596fd59 on Nov 21, 2026 and ran the checks described on the GitHub Tools page: credential patterns, decode-and-execute code, install-time scripts, committed binaries, risky CI workflows, every host the code talks to, known vulnerabilities in pinned dependencies, and project hygiene. A person read every hit. This is what we found.
- 0 secret hits and no committed binaries across 1,546 files. Its own code is about 15,000 lines of Go; most of the files are the Go libraries copied into vendor/, which are exactly what its releases are built from.
- 1 pattern hit, in .devcontainer/Dockerfile: it pipes golangci-lint's install script into sh to add a code checker to the project's development container. It does not run when you install lazydocker.
- No installer you need. scripts/install_update_linux.sh, the README's curl-to-bash option, downloads the latest release from GitHub into ~/.local/bin with no sudo and no shell edits, but does not verify a checksum. .circleci/install_snapcraft.sh uses sudo only to prepare an old CI machine.
- 37 advisories (8 critical, 8 high, 10 moderate, 2 low, 9 unrated), none in code lazydocker builds in. Releases build with -mod=vendor, and vendor/modules.txt shows that the 22 for golang.org/x/crypto, all 8 critical among them, are in its SSH packages, which are not included at all. The 5 for docker/docker are bugs in the Docker engine, while lazydocker includes only the client and API types; the 6 for OpenTelemetry are in packages it does not include; the docker/cli one is in the Windows plugin loader, also left out. That leaves 3 unrated bugs in golang.org/x/sys and golang.org/x/text.
- The program contacts no server of its own: it talks only to your Docker engine, on this machine or wherever DOCKER_HOST points, and we found no analytics or update checks. Three workflows, no pull_request_target; none of the 4 third-party actions is pinned to a commit, and checkout is still on v2. GoReleaser builds releases from version tags. No security policy file, Dependabot or CodeQL. OpenSSF Scorecard gives it 3.2 out of 10.
What the scanner counted
| Check | Result |
|---|---|
| Secrets | None found. |
| Suspicious code | 1 pattern hit found and read; every one is listed under the raw findings. |
| Install-time code | 2 installer scripts (one can call sudo) |
| Committed binaries | None. |
| CI workflows | 3 workflows. None use pull_request_target. 4 of 4 third-party actions pinned to a tag rather than a commit. |
| Network hosts | 7 distinct hosts referenced from source; most often github.com, docs.docker.com, raw.githubusercontent.com, mholt.github.io. No URLs to bare IP addresses. |
| Known vulnerabilities | 37 advisories across 71 pinned packages: 8 critical, 8 high, 10 moderate, 2 low, 9 unrated. go.mod: 71 packages, 37 advisories. |
| Project hygiene | Has licence file, contributing guide. Missing security policy, automated dependency updates, CodeQL. |
| OpenSSF Scorecard | 3.2 out of 10, as of Nov 16, 2026. |
The raw findings
Every hit the scanner wrote out, with a link to the exact line at the scanned commit. Secrets candidates are redacted.
Pattern hits (1)
| Where | Rule | Match |
|---|---|---|
| .devcontainer/Dockerfile:10 | download-piped-to-shell | RUN curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.50.0 |
Installer scripts (2)
- .circleci/install_snapcraft.sh, 26 lines, uses sudo
- scripts/install_update_linux.sh, 25 lines; talks to github.com
Worst known vulnerabilities (24 of 37)
| Advisory | Severity | Package | Summary |
|---|---|---|---|
| GHSA-5cgq-3rg8-m6cv | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status |
| GHSA-89gr-r52h-f8rx | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed |
| GHSA-f5wc-c3c7-36mc | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys |
| GHSA-jppx-rxg9-jmrx | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto doesn't enforce invoking key constraints |
| GHSA-rm3j-f69w-wqmq | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto vulnerable to infinite loop on large channel writes |
| GHSA-v778-237x-gjrc | critical | golang.org/x/crypto@0.24.0 | Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto |
| GHSA-vgwf-h737-ff37 | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: Invoking client can cause server deadlock on unexpected responses |
| GHSA-x527-x647-q7gg | critical | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement |
| GHSA-p436-gjf2-799p | high | github.com/docker/cli@27.1.1+incompatible | Docker CLI Plugins: Uncontrolled Search Path Element Leads to Local Privilege Escalation on Windows |
| GHSA-rg2x-37c3-w2rh | high | github.com/docker/docker@28.5.2+incompatible | Docker: Race condition in docker cp allows bind mount redirection to host path |
| GHSA-x86f-5xw2-fm2r | high | github.com/docker/docker@28.5.2+incompatible | Docker: `PUT /containers/{id}/archive` executes container binary on the host |
| GHSA-9h8m-3fm2-qjrq | high | go.opentelemetry.io/otel/sdk@1.28.0 | OpenTelemetry Go SDK Vulnerable to Arbitrary Code Execution via PATH Hijacking |
| GHSA-hfvc-g4fc-pqhx | high | go.opentelemetry.io/otel/sdk@1.28.0 | opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking |
| GHSA-hcg3-q754-cr77 | high | golang.org/x/crypto@0.24.0 | golang.org/x/crypto Vulnerable to Denial of Service (DoS) via Slow or Incomplete Key Exchange |
| GHSA-q4h4-gmj2-qvw2 | high | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: Invoking byte arithmetic causes underflow and panic |
| GHSA-w879-237q-wc7r | high | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: Invoking pathological RSA/DSA parameters may cause DoS |
| GHSA-pxq6-2prw-chj9 | moderate | github.com/docker/docker@28.5.2+incompatible | Moby has an Off-by-one error in its plugin privilege validation |
| GHSA-vp62-88p7-qqf5 | moderate | github.com/docker/docker@28.5.2+incompatible | Docker: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap |
| GHSA-w8rr-5gcm-pp58 | moderate | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@1.28.0 | opentelemetry-go: OTLP HTTP exporters read unbounded HTTP response bodies |
| GHSA-p9f8-wvj8-2fg8 | moderate | go.opentelemetry.io/otel/sdk@1.28.0 | OpenTelemetry-Go: UTF-8 replacement rune bypasses attribute length truncation |
| GHSA-45gg-vh54-h5m9 | moderate | golang.org/x/crypto@0.24.0 | golang.org/x/crypto vulnerable to invoking bypass of certificate restrictions |
| GHSA-78mq-xcr3-xm33 | moderate | golang.org/x/crypto@0.24.0 | golang.org/x/crypto is vulnerable to invoking server panic during CheckHostKey/Authenticate flow |
| GHSA-9m57-25v3-79x9 | moderate | golang.org/x/crypto@0.24.0 | golang.org/x/crypto: Invoking pathological inputs can lead to client panic |
| GHSA-f6x5-jh6r-wrfv | moderate | golang.org/x/crypto@0.24.0 | golang.org/x/crypto/ssh/agent vulnerable to panic if message is malformed due to out of bounds read |
By the numbers
| Stars | 53.4K |
|---|---|
| Forks | 1,734 |
| Contributors | 90 |
| Commits | 893 |
| Open issues | 206 |
| Open pull requests | 105 |
| Releases | 47 |
| Latest release | v0.25.2 |
| Licence | MIT |
| Main language | Go |
| Project age | 7 years |
| Last push | Nov 15, 2026 |
| Tracked files | 1,546 |
| Lines of code | 15K |
| Checkout size | 27 MB |
Lines by language: Go 12.6K, Markdown 1,705, YAML 481, Shell 122, JSON 71.
Questions
Is lazydocker free?
Yes. It is free and open source under the MIT licence, with no paid version. The README opens with a job ad from a sponsor, Subble, and links GitHub Sponsors.
lazydocker or Docker Desktop?
lazydocker if you want a fast keyboard view of containers and logs in the terminal, including on a server over SSH. Docker Desktop is the app that installs and runs Docker itself on Mac and Windows; lazydocker needs Docker already running, so many people use both.
Does lazydocker work on Windows?
Yes. Install it with Scoop or Chocolatey and run it in Windows Terminal while Docker Desktop is running.
Does lazydocker send my data anywhere?
No. It only talks to your Docker engine to list containers and read logs and stats. We found no analytics, telemetry or update checks.
How do I uninstall lazydocker?
Run brew uninstall lazydocker or scoop uninstall lazydocker, remove any alias you added, and delete its config folder if you want your settings gone.
This post is part of GitHub Tools, where every repository is cloned and scanned before it is written up. The scan is a snapshot of one commit on one day; the repository has moved on since, so check it before you install.
