Distroless

Distroless provides minimal base container images that contain only your application and its runtime dependencies, with no package manager, shell, or other…

  • Infrastructure
  • Tools & Utilities
Distroless provides minimal base container images that contain only your application and its runtime dependencies, with no package manager, shell, or other programs. They are suited to production container deployments where you want the smallest possible image size and the tightest attack surface.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

81/100 Excellent

Maintained
100last commit 1 day ago
Popular
8723,286 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
94no serious findings, CI, tests, OpenSSF Scorecard 8.5/10

Based on 4 of 5 factors.

GitHub stars
23,286
Open issues
13
Last commit
2026-11-20
License
Apache-2.0
Activity
rising

Checked yesterday - source: GitHub (GoogleContainerTools/distroless)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use the debug image to get a shell Standard Distroless images do not include a shell, so you cannot log in or run commands to fix things; use the debug image and start it with sh to inspect files and troubleshoot. source
  • Map web ports with -p For a web app like the Node.js example, add -p 3000:3000 to docker run so your computer can reach the container; without it, the app runs but you cannot open it in a browser. source
  • Write ENTRYPOINT as a list Because Distroless has no shell, set ENTRYPOINT in your Dockerfile using the list form, like ["myapp"]; the simple string form can cause the container to fail to start. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I troubleshoot a Distroless container when it has no shell?

Standard Distroless images do not include a shell, so you cannot log in or run commands. Use the debug image and start it with sh to inspect files and troubleshoot.

Why might a Distroless container fail to start because of the Dockerfile ENTRYPOINT?

Because Distroless has no shell, set ENTRYPOINT in the list form, such as ["myapp"]. The simple string form can cause the container to fail to start.

How do I make a web app in a Distroless container reachable from a browser?

Map the web port with -p, for example -p 3000:3000 on docker run. Without the port mapping, the app can run but you cannot open it in a browser.

Which Distroless image tags are currently updated?

The published and updated tags include latest, nonroot, debug, and debug-nonroot. You can reference architecture-specific images by adding a suffix such as latest-amd64, and other tags are considered deprecated.

Can I use Distroless images without building them with Bazel?

Yes. The images are built using Bazel, but they can also be used through other Docker image build tooling.

Answers sourced from github.com, github.com

Community

Collected 48 days ago - public community threads