public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 14:21:32 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/clickhouse] Release 23.3.19-debian-11-r1 (#54937)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-01-19 18:53:15 +01:00
committed by GitHub
parent 3909d6c2c4
commit 45f77a5880
2 changed files with 42 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/clickhouse/23.3/debian-11/Dockerfile
+3 -2
View File
@@ -7,10 +7,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2024-01-05T19:04:14Z" \
org.opencontainers.image.created="2024-01-19T16:37:29Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="23.3.19-debian-11-r0" \
org.opencontainers.image.ref.name="23.3.19-debian-11-r1" \
org.opencontainers.image.title="clickhouse" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="23.3.19"
@@ -41,6 +41,7 @@ RUN apt-get autoremove --purge -y curl && \
apt-get update && apt-get upgrade -y && \
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
RUN chmod g+rwX /opt/bitnami
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/clickhouse/postunpack.sh
bitnami/clickhouse/README.md
+39 -22
View File
@@ -13,13 +13,6 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name clickhouse bitnami/clickhouse:latest
```
### Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/clickhouse/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
## Why use Bitnami Images?
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
@@ -196,13 +189,41 @@ When the container is executed for the first time, it will execute the files wit
In order to have your custom files inside the docker image you can mount them as a volume.
### Environment variables
#### Customizable environment variables
| Name | Description | Default Value |
|------------------------------------|-------------------------------|---------------|
| `ALLOW_EMPTY_PASSWORD` | Allow an empty password. | `no` |
| `CLICKHOUSE_ADMIN_USER` | ClickHouse admin username. | `default` |
| `CLICKHOUSE_HTTP_PORT` | ClickHouse HTTP port. | `8123` |
| `CLICKHOUSE_TCP_PORT` | ClickHouse TCP port. | `9000` |
| `CLICKHOUSE_MYSQL_PORT` | ClickHouse MySQL port. | `9004` |
| `CLICKHOUSE_POSTGRESQL_PORT` | ClickHouse PostgreSQL port. | `9005` |
| `CLICKHOUSE_INTERSERVER_HTTP_PORT` | ClickHouse Inter-server port. | `9009` |
#### Read-only environment variables
| Name | Description | Value |
|-------------------------------|-------------------------------------|----------------------------------------------|
| `CLICKHOUSE_BASE_DIR` | ClickHouse installation directory. | `${BITNAMI_ROOT_DIR}/clickhouse` |
| `CLICKHOUSE_VOLUME_DIR` | ClickHouse volume directory. | `/bitnami/clickhouse` |
| `CLICKHOUSE_CONF_DIR` | ClickHouse configuration directory. | `${CLICKHOUSE_BASE_DIR}/etc` |
| `CLICKHOUSE_MOUNTED_CONF_DIR` | ClickHouse configuration directory. | `${CLICKHOUSE_VOLUME_DIR}/etc` |
| `CLICKHOUSE_DATA_DIR` | ClickHouse data directory. | `${CLICKHOUSE_VOLUME_DIR}/data` |
| `CLICKHOUSE_LOG_DIR` | ClickHouse logs directory. | `${CLICKHOUSE_BASE_DIR}/logs` |
| `CLICKHOUSE_CONF_FILE` | ClickHouse log file. | `${CLICKHOUSE_CONF_DIR}/config.xml` |
| `CLICKHOUSE_LOG_FILE` | ClickHouse log file. | `${CLICKHOUSE_LOG_DIR}/clickhouse.log` |
| `CLICKHOUSE_ERROR_LOG_FILE` | ClickHouse log file. | `${CLICKHOUSE_LOG_DIR}/clickhouse_error.log` |
| `CLICKHOUSE_TMP_DIR` | ClickHouse temporary directory. | `${CLICKHOUSE_BASE_DIR}/tmp` |
| `CLICKHOUSE_PID_FILE` | ClickHouse PID file. | `${CLICKHOUSE_TMP_DIR}/clickhouse.pid` |
| `CLICKHOUSE_INITSCRIPTS_DIR` | ClickHouse init scripts directory. | `/docker-entrypoint-initdb.d` |
| `CLICKHOUSE_DAEMON_USER` | ClickHouse daemon system user. | `clickhouse` |
| `CLICKHOUSE_DAEMON_GROUP` | ClickHouse daemon system group. | `clickhouse` |
### Setting the admin password on first run
The admin user and password can easily be setup with the Bitnami ClickHouse Docker image using the following environment variables:
* `CLICKHOUSE_ADMIN_USER`: The database admin user. Defaults to `default`.
* `CLICKHOUSE_ADMIN_PASSWORD`: The database admin user password. No defaults.
Passing the `CLICKHOUSE_ADMIN_PASSWORD` environment variable when running the image for the first time will set the password of the `CLICKHOUSE_ADMIN_USER` user to the value of `CLICKHOUSE_ADMIN_PASSWORD`.
```console
@@ -220,16 +241,6 @@ services:
...
```
### Changing the default ports
ClickHouse default ports can be changed using the following environment variables:
* `CLICKHOUSE_HTTP_PORT`: HTTP port. Defaults to `8123`.
* `CLICKHOUSE_TCP_PORT`: TCP port. Defaults to `9000`.
* `CLICKHOUSE_MYSQL_PORT`: MySQL port. Defaults to `9004`.
* `CLICKHOUSE_POSTGRESQL_PORT`: PostgreSQL port. Defaults to `9005`.
* `CLICKHOUSE_INTERSERVER_HTTP_PORT`: Inter-server HTTP port. Defaults to `9009`.
### Allowing empty passwords
By default the ClickHouse image expects all the available passwords to be set. In order to allow empty passwords, it is necessary to set the `ALLOW_EMPTY_PASSWORD=yes` env variable. This env variable is only recommended for testing or development purposes. We strongly recommend specifying the `CLICKHOUSE_ADMIN_PASSWORD` for any other scenario.
@@ -319,6 +330,12 @@ or using Docker Compose:
docker-compose up clickhouse
```
## 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).
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.