[bitnami/clickhouse-keeper] Release 26.4.1-debian-12-r0 (#92801)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-05-05 22:09:04 +02:00
committed by GitHub
parent f2d32b6a5a
commit 7a78014cdc
2 changed files with 13 additions and 11 deletions
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-14T14:45:19Z" \
org.opencontainers.image.created="2026-05-05T19:53:13Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/clickhouse-keeper/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/clickhouse-keeper" \
org.opencontainers.image.title="clickhouse-keeper" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="26.3.9"
org.opencontainers.image.version="26.4.1"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"clickhouse-keeper-26.3.9-0-linux-${OS_ARCH}-debian-12" \
"clickhouse-keeper-26.4.1-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -47,7 +47,7 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/clickhouse-keeper/postunpack.sh
ENV APP_VERSION="26.3.9" \
ENV APP_VERSION="26.4.1" \
BITNAMI_APP_NAME="clickhouse-keeper" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/clickhouse-keeper/bin:/opt/bitnami/common/bin:$PATH" \
+9 -7
View File
@@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name clickhouse-keeper bitnami/clickhouse-keeper:latest
```
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/clickhouse-keeper/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/clickhouse-keeper/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/clickhouse).
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@@ -118,13 +126,7 @@ The Bitnami ClickHouse Keeper Docker image from the [Bitnami Secure Images](http
## Logging
The Bitnami ClickHouse Keeper Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs clickhouse-keeper
```
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.
The Bitnami ClickHouse Keeper Docker image sends the container logs to the `stdout`. 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.
## License