"Distroless" images contain only your application and its runtime dependencies. They do not contain package managers, shells or any other programs you would expect to find in a standard Linux distribution.
For more information, see this talk (video).
Since March 2023, Distroless images use oci manifests, if you see errors referencing application/vnd.oci.image.manifest.v1+json
or application/vnd.oci.image.index.v1+json, update your container tooling (docker, jib, etc) to latest.
Restricting what's in your runtime container to precisely what's necessary for your app is a best practice employed by Google and other tech giants that have used containers in production for many years. It improves the signal to noise of scanners (e.g. CVE) and reduces the burden of establishing provenance to just what you need.
Distroless images are very small.
The smallest distroless image, gcr.io/distroless/static-debian11, is around 2 MiB.
That's about 50% of the size of alpine (~5 MiB), and less than 2% of the size of debian (124 MiB).
These images are built using bazel, but they can also be used through other Docker image build tooling.
The following images are currently published and updated by the distroless project (see SUPPORT_POLICY for support timelines)
| Image | Tags | Architecture Suffixes |
|---|---|---|
| gcr.io/distroless/static-debian12 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/base-debian12 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/base-nossl-debian12 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/cc-debian12 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/static-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/base-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/base-nossl-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/cc-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, arm, s390x, ppc64le |
| gcr.io/distroless/python3-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64 |
| gcr.io/distroless/java-base-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, s390x, ppc64le |
| gcr.io/distroless/java11-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, s390x, ppc64le |
| gcr.io/distroless/java17-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64, s390x, ppc64le |
| gcr.io/distroless/nodejs16-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64 |
| gcr.io/distroless/nodejs18-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64 |
| gcr.io/distroless/nodejs20-debian11 | latest, nonroot, debug, debug-nonroot | amd64, arm64 |
These images refer to image indexes with references to all supported architectures. Architecture specific images can be directly referenced using an additional architecture suffix on the tag, like gcr.io/distroless/static-debian11:latest-amd64
Any other tags are considered deprecated and are no longer updated
All distroless images are signed by cosign. We recommend verifying any distroless image you use before building your image.
Distroless images are signed with cosign in keyless mode. You can verify the keyless signature of any distroless image with:
cosign verify $IMAGE_NAME --certificate-oidc-issuer https://accounts.google.com --certificate-identity [email protected]
Verifying using the distroless keys is deprecated in favor of keyless. These signing events are not uploaded to the transparency log. You can use the distroless public key to verify any distroless image with:
cat cosign.pub
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZzVzkb8A+DbgDpaJId/bOmV8n7Q
OqxYbK0Iro6GzSmOzxkn+N2AKawLyXi84WSwJQBK//psATakCgAQKkNTAA==
-----END PUBLIC KEY-----
cosign verify --key cosign.pub $IMAGE_NAME --insecure-ignore-tlog
Note that distroless images by default do not contain a shell.
That means the Dockerfile ENTRYPOINT command, when defined, must be specified in vector form, to avoid the container runtime prefixing with a shell.
This works:
ENTRYPOINT ["myapp"]
But this does not work:
ENTRYPOINT "myapp"
For the same reasons, if the entrypoint is set to the empty vector, the CMD command should be specified in vector form (see examples below).
Note that by default static, base and cc images have the empty vector entrypoint. Images with an included language runtime have a language specific default (see: java, nodejs, python3).
Docker multi-stage builds make using distroless images easy. Follow these steps to get started:
-
Pick the right base image for your application stack. We publish the following distroless base images on
gcr.io:- gcr.io/distroless/static-debian12
- gcr.io/distroless/static-debian11
- gcr.io/distroless/base-nossl-debian12
- gcr.io/distroless/base-nossl-debian11
- gcr.io/distroless/base-debian12
- gcr.io/distroless/base-debian11
- gcr.io/distroless/java11-debian11
- gcr.io/distroless/java17-debian11
- gcr.io/distroless/cc-debian12
- gcr.io/distroless/cc-debian11
- gcr.io/distroless/nodejs16-debian11
- gcr.io/distroless/nodejs18-debian11
- gcr.io/distroless/nodejs20-debian11
-
The following images are also published on
gcr.io, but are considered experimental and not recommended for production usage: -
Write a multi-stage docker file. Note: This requires Docker 17.05 or higher.
The basic idea is that you'll have one stage to build your application artifacts, and insert them into your runtime distroless image. If you'd like to learn more, please see the documentation on multi-stage builds.
Here's a quick example for go:
# Start by building the application.
FROM golang:1.18 as build
WORKDIR /go/src/app
COPY . .
RUN go mod download
RUN CGO_ENABLED=0 go build -o /go/bin/app
# Now copy it into our base image.
FROM gcr.io/distroless/static-debian11
COPY --from=build /go/bin/app /
CMD ["/app"]You can find other examples here:
To run any example, go to the directory for the language and run
docker build -t myapp .
docker run -t myapp
To run the Node.js Express app node-express and expose the container's ports:
npm install # Install express and its transitive dependencies
docker build -t myexpressapp . # Normal build command
docker run -p 3000:3000 -t myexpressapp
This should expose the Express application to your localhost:3000
For full documentation on how to use bazel to generate Container images, see the bazel-contrib/rules_oci repository.
For documentation and example on how to use the go-based debian package manager (current) to generate bazel config, see ./debian_package_manager For documentation and examples on how to use the bazel package manager rules (not used in this repo), see ./package_manager
Examples can be found in this repository in the examples directory.
We have some examples on how to run some common application stacks in the /examples directory. See here for:
See here for examples on how to complete some common tasks in your image:
- Adding and running as a non-root user
- Including debian packages (TBD, currently in private)
- Including CA certificates
See here for more information on how these images are built and released.
Distroless images are based on Debian 11 (bullseye) and Debian 12 (bookworm). Images are explicitly tagged with Debian version suffixes (e.g. -debian11). Specifying an image without the distribution will currently select -debian11 images, but that will change in the future to a newer version of Debian. It can be useful to reference the distribution explicitly, to prevent breaking builds when the next Debian version is released.
Distroless tracks the upstream Debian releases, using Github actions to automatically generate a pull request when there are updates.
Distroless images are minimal and lack shell access. The :debug image set for each language provides a busybox shell to enter.
For example:
cd examples/python3/
edit the Dockerfile to change the final image to :debug:
FROM gcr.io/distroless/python3-debian11:debug
COPY . /app
WORKDIR /app
CMD ["hello.py", "/etc"]then build and launch with an shell entrypoint:
$ docker build -t my_debug_image .
$ docker run --entrypoint=sh -ti my_debug_image
/app # ls
BUILD Dockerfile hello.py
Note: If the image you are using already has a tag, for example
gcr.io/distroless/java17-debian11:nonroot, use the tagdebug-<existing tag>instead, for examplegcr.io/distroless/java17-debian11:debug-nonroot.
Note: ldd is not installed in the base image as it's a shell script, you can copy it in or download it.
- Kubernetes, since v1.15
- Knative
- Tekton
If your project uses Distroless, send a PR to add your project here!