Getting Started
Install docker-doctor and run your first scan.
On this page
Install
docker-doctor is published as @docker-doctor/cli. There's nothing to install permanently — run it directly with npx or bunx:
npx @docker-doctor/cli@latestbunx @docker-doctor/cli@latestRun a scan
By default docker-doctor scans the current directory for Dockerfiles and Compose files:
npx @docker-doctor/cli@latest .You can point it at any directory:
npx @docker-doctor/cli@latest ./path/to/projectRead the output
A scan prints one line per diagnostic — the file and line, the severity, a short message, and the rule key that raised it — followed by an overall health score:
Dockerfile
10:1 warning Container should not run as root user docker-doctor/no-root-user
Score: 94 Good ✅Add --verbose to see the affected file, an explanation, and a Help: fix hint for every diagnostic:
npx @docker-doctor/cli@latest . --verboseThe scan exits non-zero when any error-severity diagnostic is present, which makes it a natural CI gate — after your first scan, docker-doctor will offer to wire up a GitHub Actions workflow for you.
Next steps
- Browse every rule with
npx @docker-doctor/cli@latest rules list, or read the full list in Rules. - See all flags and exit codes in the CLI reference.
- Tune rule severities or ignore files in Configuration.
- Understand how the health score is calculated in Scoring.