From 9834425149549146308feddbc6fc860d8b99855b Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 19 Feb 2026 14:54:33 +0100 Subject: [PATCH] [bitnami/clickhouse-keeper] Release 26.1.3-debian-12-r0 (#91005) Signed-off-by: Bitnami Bot --- .../clickhouse-keeper/26/debian-12/Dockerfile | 10 +- bitnami/clickhouse-keeper/README.md | 142 ------------------ 2 files changed, 5 insertions(+), 147 deletions(-) diff --git a/bitnami/clickhouse-keeper/26/debian-12/Dockerfile b/bitnami/clickhouse-keeper/26/debian-12/Dockerfile index 33e35600ff68..40b98471f613 100644 --- a/bitnami/clickhouse-keeper/26/debian-12/Dockerfile +++ b/bitnami/clickhouse-keeper/26/debian-12/Dockerfile @@ -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-02-19T01:02:30Z" \ + org.opencontainers.image.created="2026-02-19T13:44:06Z" \ 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.1.2" + org.opencontainers.image.version="26.1.3" 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.1.2-0-linux-${OS_ARCH}-debian-12" \ + "clickhouse-keeper-26.1.3-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -47,9 +47,9 @@ RUN uninstall_packages curl COPY rootfs / RUN /opt/bitnami/scripts/clickhouse-keeper/postunpack.sh -ENV APP_VERSION="26.1.2" \ +ENV APP_VERSION="26.1.3" \ BITNAMI_APP_NAME="clickhouse-keeper" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="0" \ PATH="/opt/bitnami/clickhouse-keeper/bin:/opt/bitnami/common/bin:$PATH" \ clickhouseCTL_API="3" diff --git a/bitnami/clickhouse-keeper/README.md b/bitnami/clickhouse-keeper/README.md index c8b3e22d0061..8a3ff2cfdf65 100644 --- a/bitnami/clickhouse-keeper/README.md +++ b/bitnami/clickhouse-keeper/README.md @@ -62,94 +62,12 @@ If you remove the container all your data will be lost, and the next time you ru For persistence you should mount a directory at the `/bitnami/clickhouse-keeper` path. If the mounted directory is empty, it will be initialized on the first run. -```console -docker run \ - --volume /path/to/clickhouse-keeper-persistence:/bitnami/clickhouse-keeper \ - bitnami/clickhouse-keeper:latest -``` - -You can also do this with a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/clickhouse-keeper/docker-compose.yml) file present in this repository: - -```console -clickhouse-keeper: - ... - volumes: - - /path/to/clickhouse-keeper-persistence:/bitnami/clickhouse-keeper - ... -``` - ## Connecting to other containers Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa. Containers attached to the same network can communicate with each other using the container name as the hostname. -### Using the Command Line - -In this example, we will create a ClickHouse Keeper client instance that will connect to the ClickHouse Keeper instance that is running on the same docker network as the client. - -#### Step 1: Create a network - -```console -docker network create my-network --driver bridge -``` - -#### Step 2: Launch the ClickHouse Keeper container within your network - -Use the `--network ` argument to the `docker run` command to attach the container to the `my-network` network. - -```console -docker run -d --name clickhouse-keeper \ - --env CLICKHOUSE_KEEPER_SERVER_ID=1 \ - --network my-network \ - bitnami/clickhouse-keeper:latest -``` - -#### Step 3: Launch your ClickHouse Keeper client instance - -Finally we create a new container instance to launch the ClickHouse Keeper client and connect to the ClickHouse Keeper created in the previous step: - -```console -docker run -it --rm \ - --network my-network \ - bitnami/clickhouse-keeper:latest clickhouse-keeper-client --host clickhouse-keeper -``` - -### Using a Docker Compose file - -When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `my-network`. In this example we assume that you want to connect to the ClickHouse Keeper from your own custom application image which is identified in the following snippet by the service name `myapp`. - -```yaml -version: '2' - -networks: - my-network: - driver: bridge - -services: - clickhouse-keeper: - image: bitnami/clickhouse-keeper:latest - environment: - - CLICKHOUSE_KEEPER_SERVER_ID=1 - networks: - - my-network - myapp: - image: YOUR_APPLICATION_IMAGE - networks: - - my-network -``` - -> **IMPORTANT**: -> -> 1. Please update the `YOUR_APPLICATION_IMAGE` placeholder in the above snippet with your application image -> 2. In your application container, use the hostname `clickhouse-keeper` to connect to the ClickHouse Keeper server - -Launch the containers using: - -```console -docker-compose up -d -``` - ## Configuration ClickHouse Keeper can be configured via environment variables or using a configuration file (`keeper_config.xml`). If a configuration option is not specified in either the configuration file or in an environment variable, ClickHouse Keeper uses its internal default configuration. @@ -226,66 +144,6 @@ 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. -## Maintenance - -### Upgrade this image - -Bitnami provides up-to-date versions of ClickHouse Keeper, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. - -#### Step 1: Get the updated image - -```console -docker pull bitnami/clickhouse-keeper:latest -``` - -or if you're using Docker Compose, update the value of the image property to `bitnami/clickhouse-keeper:latest`. - -#### Step 2: Stop and backup the currently running container - -Stop the currently running container using the command - -```console -docker stop clickhouse-keeper -``` - -or using Docker Compose: - -```console -docker-compose stop clickhouse-keeper -``` - -Next, take a snapshot of the persistent volume `/path/to/clickhouse-keeper-persistence` using: - -```console -rsync -a /path/to/clickhouse-keeper-persistence /path/to/clickhouse-keeper-persistence.bkp.$(date +%Y%m%d-%H.%M.%S) -``` - -#### Step 3: Remove the currently running container - -```console -docker rm -v clickhouse-keeper -``` - -or using Docker Compose: - -```console -docker-compose rm -v clickhouse-keeper -``` - -#### Step 4: Run the new image - -Re-create your container from the new image. - -```console -docker run --name clickhouse-keeper bitnami/clickhouse-keeper:latest -``` - -or using Docker Compose: - -```console -docker-compose up clickhouse-keeper -``` - ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.