Request
Please cut a release (patch or minor) so that a versioned -distroless image tag is published to Docker Hub / quay.io.
Background
The distroless image variant was added in July, but because it landed after v0.19.0, the only distroless tag currently available is main-distroless, which is rebuilt continuously from main. There is no v0.19.0-distroless or any other versioned distroless tag. Sibling Prometheus projects already publish versioned distroless tag, so this appears to be a timing issue vs. an intentional exclusion.
Why this matters to us
We run mysqld_exporter as a sidecar across a large production fleet. The busybox-based image carries base-OS CVEs that the
distroless base does not. We compared the two variants and confirmed that switching to distroless clears all of the outstanding findings we currently track for this image, with no change in exported metrics.
The blocker is purely the lack of a versioned tag: we can't ship a rolling main build to production, and our automated image-update tooling tracks semver tags per variant, so main-distroless isn't something we can adopt.
Other
I'd be happy to help test a release candidate against one of our MySQL fleets if that's useful. Thanks!
Request
Please cut a release (patch or minor) so that a versioned
-distrolessimage tag is published to Docker Hub / quay.io.Background
The distroless image variant was added in July, but because it landed after v0.19.0, the only distroless tag currently available is
main-distroless, which is rebuilt continuously frommain. There is nov0.19.0-distrolessor any other versioned distroless tag. Sibling Prometheus projects already publish versioned distroless tag, so this appears to be a timing issue vs. an intentional exclusion.Why this matters to us
We run mysqld_exporter as a sidecar across a large production fleet. The busybox-based image carries base-OS CVEs that the
distroless base does not. We compared the two variants and confirmed that switching to distroless clears all of the outstanding findings we currently track for this image, with no change in exported metrics.
The blocker is purely the lack of a versioned tag: we can't ship a rolling
mainbuild to production, and our automated image-update tooling tracks semver tags per variant, somain-distrolessisn't something we can adopt.Other
I'd be happy to help test a release candidate against one of our MySQL fleets if that's useful. Thanks!