[bitnami/thanos] Release 0.41.0-debian-12-r2 (#92030)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-05 21:11:51 +02:00
committed by GitHub
parent 5710d89c6a
commit b759f19e2e
2 changed files with 9 additions and 2 deletions
+2 -2
View File
@@ -40,7 +40,7 @@ ARG TARGETARCH
ENV OS_ARCH="${TARGETARCH:-amd64}"
LABEL org.opencontainers.image.base.name="scratch" \
org.opencontainers.image.created="2026-03-06T18:32:29Z" \
org.opencontainers.image.created="2026-04-05T19:04:29Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.title="thanos" \
org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -53,7 +53,7 @@ COPY --from=builder /opt/bitnami/thanos/licenses /opt/bitnami/thanos/licenses
ENV APP_VERSION="0.41.0" \
BITNAMI_APP_NAME="thanos" \
IMAGE_REVISION="1" \
IMAGE_REVISION="2" \
PATH="/opt/bitnami/thanos/bin:$PATH"
USER 1001
+7
View File
@@ -104,6 +104,13 @@ docker logs thanos
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
### FIPS configuration in Bitnami Secure Images
The Bitnami Thanos Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
- `GODEBUG`: controls Go FIPS mode. Use `fips140=only` (restricted), `fips140=on` (relaxed), or `fips140=off` (disabled).
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.