distroless icon indicating copy to clipboard operation
distroless copied to clipboard

🥑 Language focused docker images, minus the operating system.

Results 147 distroless issues
Sort by recently updated
recently updated
newest added

Hello, is there any more allegiant solution for using python 3.12, 3.13 than https://github.com/GoogleContainerTools/distroless/issues/1543#issuecomment-2432044825 ? now i do understand nothing about bazel to do it myself. Maybe you can recommend...

Hi team, I'm currently building a Docker image using gcr.io/distroless/nodejs22-debian12:nonroot as the base for the production stage. Here's the relevant part of the Dockerfile: ``` Dockerfile FROM gcr.io/distroless/nodejs22-debian12:nonroot AS production...

Since a few of our applications can't be migrated to Java 17 or Java 21 runtimes yet, we would like to kindly ask if it's possible to provide Java 11...

**Describe the bug** When I use `cosign download attestation` with a platform, I get the SBOM twice... Is there a reason for this? 😅 **To Reproduce** Assuming that `cosign` and...

Currently we need to add "magic", absolute path to node binary in health cmd: ```Dockerfile # myapp CMD [ "./server.js" ] HEALTHCHECK CMD [ "/nodejs/bin/node", "./healthcheck.js" ] ``` If we...

In our project, we have set up dependabot to check on every Monday if there are new node.js distroless images. We also do a trivy scan to compare the old...

**Describe the bug** When running `bazel run @bullseye://.lock` without an existing `bullseye.lock.json` file present, the command fails with the error: ``` Error in read: java.io.FileNotFoundException: /home/qdii/dev/rules_distroless/e2e/smoke/bullseye.lock.json (No such file or...

Hey, I am trying to understand how the distroless images are being build with bazel. And in the next step I want to adjust the code to build the python...

Hey, we are currently running into issues while migrating onto an distroless image for our aws lambdas. I was following the docs from aws on how to use a non-AWS...

Debian 13 is [just around the corner](https://lists.debian.org/debian-devel-announce/2025/07/msg00003.html). Any plans to support it? Do you welcome/need community contribution on this?