Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-29 00:09:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/clickhouse] Release 26.2.1-debian-12-r0 (#91162)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-27 22:11:27 +01:00
committed by GitHub
parent 8c4b6a1f03
commit 38ffe0968b
2 changed files with 25 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/clickhouse/26/debian-12/Dockerfile
View File

@@ -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-19T13:44:11Z" \
org.opencontainers.image.created="2026-02-27T20:58:02Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/clickhouse/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/clickhouse" \
org.opencontainers.image.title="clickhouse" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="26.1.3"
org.opencontainers.image.version="26.2.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-26.1.3-0-linux-${OS_ARCH}-debian-12" \
"clickhouse-26.2.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/postunpack.sh
ENV APP_VERSION="26.1.3" \
ENV APP_VERSION="26.2.1" \
BITNAMI_APP_NAME="clickhouse" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/clickhouse/bin:/opt/bitnami/common/bin:$PATH" \

40
bitnami/clickhouse/README.md
View File

@@ -1,19 +1,19 @@
# Bitnami Secure Image for ClickHouse
## What is ClickHouse?
> ClickHouse is an open-source column-oriented OLAP database management system. Use it to boost your database performance while providing linear scalability and hardware efficiency.
[Overview of ClickHouse](https://clickhouse.com/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
## <a id="tl-dr"></a> TL;DR
Use this quick command to run the container.
```console
docker run --name clickhouse bitnami/clickhouse:latest
```
## Why use Bitnami Secure Images?
## <a id="why-use-bitnami-secure-images"></a> 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?
@@ -30,15 +30,15 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## How to deploy ClickHouse in Kubernetes?
## <a id="deploy-in-kubernetes"></a> How to deploy ClickHouse in Kubernetes
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami ClickHouse Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/clickhouse).
## Supported tags and respective `Dockerfile` links
## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## Get this image
## <a id="get-this-image"></a> Get this image
The recommended way to get the Bitnami ClickHouse Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/clickhouse).
@@ -60,41 +60,43 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## Using `docker-compose.yaml`
## <a id="using-docker-compose"></a> Using `docker-compose.yaml`
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).
## Persisting your application
## <a id="persisting-your-application"></a> Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the `/bitnami/clickhouse` path. If the mounted directory is empty, it will be initialized on the first run.
## Connecting to other containers
## <a id="connecting-to-other-containers"></a> 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.
## Configuration
## <a id="configuration"></a> Configuration
ClickHouse can be configured via environment variables or using a configuration file (`config.xml`). If a configuration option is not specified in either the configuration file or in an environment variable, ClickHouse uses its internal default configuration.
ClickHouse can be configured using environment variables or a configuration file (`config.xml`). If a configuration option is not specified in either the configuration file or in an environment variable, ClickHouse uses its internal default configuration.
### Configuration overrides
### <a id="configuration-overrides"></a> Configuration overrides
The configuration can easily be setup by mounting your own configuration overrides on the directory `/bitnami/clickhouse/etc/config.d` or `/bitnami/clickhouse/etc/users.d`.
Check the [official ClickHouse configuration documentation](https://clickhouse.com/docs/en/operations/configuration-files/) for all the possible overrides and settings.
### Initializing a new instance
### <a id="initializing-new-instance"></a> Initializing a new instance
When the container is executed for the first time, it will execute the files with extensions `.sh` located at `/docker-entrypoint-initdb.d`. For scripts to be executed every time the container starts, use the `/docker-entrypoint-startdb.d` folder.
In order to have your custom files inside the docker image you can mount them as a volume.
> NOTE: If you use JSON format for clickhouse logs and remove the message field of the logs, the application will fail to start if there are init or start scripts in any of those 2 folders.
> **NOTE** If you use JSON format for ClickHouse logs and remove the message field of the logs, the application will fail to start if there are init or start scripts in any of those 2 folders.
### Environment variables
### <a id="environment-variables"></a> Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -130,13 +132,13 @@ In order to have your custom files inside the docker image you can mount them as
| `CLICKHOUSE_DAEMON_USER` | ClickHouse daemon system user. | `clickhouse` |
| `CLICKHOUSE_DAEMON_GROUP` | ClickHouse daemon system group. | `clickhouse` |
### FIPS configuration in Bitnami Secure Images
### <a id="fips-configuration-in-bitnami-secure-images"></a> FIPS configuration in Bitnami Secure Images
The Bitnami ClickHouse 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`.
## Logging
## <a id="logging"></a> Logging
The Bitnami ClickHouse Docker image sends the container logs to `stdout`. To view the logs:
@@ -146,7 +148,7 @@ docker logs clickhouse
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
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.