bitnami-containers/bitnami/ksql/README.md

10 KiB

Bitnami Secure Image for Confluent KSQL DB

What is Confluent KSQL DB?

ksqlDB is a database for building stream processing applications on top of Apache Kafka. It is distributed, scalable, reliable, and real-time.

Overview of Confluent KSQL DB 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

docker run --name ksql bitnami/ksql:latest

⚠️ Important Notice: Upcoming changes to the Bitnami Catalog

Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new Bitnami Secure Images initiative. As part of this transition:

  • Granting community users access for the first time to security-optimized versions of popular container images.
  • Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes
  • Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
  • For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support.

These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the Bitnami Secure Images announcement.

Why use Bitnami Secure Images?

  • Bitnami Secure Images and Helm charts are built to make open source more secure and enterprise ready.
  • Triage security vulnerabilities faster, with transparency into CVE risks using industry standard Vulnerability Exploitability Exchange (VEX), KEV, and EPSS scores.
  • Our hardened images use a minimal OS (Photon Linux), which reduces the attack surface while maintaining extensibility through the use of an industry standard package format.
  • Stay more secure and compliant with continuously built images updated within hours of upstream patches.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • Hardened images come with attestation signatures (Notation), SBOMs, virus scan reports and other metadata produced in an SLSA-3 compliant software factory.

Only a subset of BSI applications are available for free. Looking to access the entire catalog of applications as well as enterprise support? Try the commercial edition of Bitnami Secure Images today.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo.

Get this image

The recommended way to get the Bitnami ksql Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/ksql:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/ksql:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .

Environment variables

Customizable environment variables

Name Description Default Value
KSQL_MOUNTED_CONF_DIR Directory for including custom configuration files (that override the default generated ones) ${KSQL_VOLUME_DIR}/etc
KSQL_LISTENERS Comma-separated list of listeners that listen for API requests over either HTTP or HTTPS. nil
KSQL_SSL_KEYSTORE_PASSWORD Password to access the SSL keystore. nil
KSQL_SSL_TRUSTSTORE_PASSWORD Password to access the SSL truststore. nil
KSQL_CLIENT_AUTHENTICATION Client authentication configuration. Valid options: none, requested, over required. nil
KSQL_BOOTSTRAP_SERVERS The set of Kafka brokers to bootstrap Kafka cluster information from. nil

Read-only environment variables

Name Description Value
KSQL_BASE_DIR Base path for KSQL files. ${BITNAMI_ROOT_DIR}/ksql
KSQL_VOLUME_DIR KSQL directory for persisted files. ${BITNAMI_VOLUME_DIR}/ksql
KSQL_DATA_DIR KSQL data directory. ${KSQL_VOLUME_DIR}/data
KSQL_BIN_DIR KSQL bin directory. ${KSQL_BASE_DIR}/bin
KSQL_CONF_DIR KSQL configuration directory. ${KSQL_BASE_DIR}/etc/ksqldb
KSQL_LOGS_DIR KSQL logs directory. ${KSQL_BASE_DIR}/logs
KSQL_CONF_FILE Main KSQL configuration file. ${KSQL_CONF_DIR}/ksql-server.properties
KSQL_CERTS_DIR KSQL certificates directory. ${KSQL_BASE_DIR}/certs
KSQL_CONNECTION_TIMEOUT KSQL connection attempt timeout. 10
KSQL_DAEMON_USER Users that will execute the KSQL Server process. ksql
KSQL_DAEMON_GROUP Group that will execute the KSQL Server process. ksql
KSQL_DEFAULT_LISTENERS Comma-separated list of listeners that listen for API requests over either HTTP or HTTPS. http://0.0.0.0:8088
KSQL_DEFAULT_BOOTSTRAP_SERVERS List of Kafka brokers to bootstrap Kafka cluster information from. localhost:9092

FIPS configuration in Bitnami Secure Images

The Bitnami Confluent KSQL DB Docker image from the Bitnami Secure Images 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.

Notable Changes

Starting January 16, 2024

  • The docker-compose.yaml file has been removed, as it was solely intended for internal testing purposes.

Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue or submitting a pull request with your contribution.

Issues

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to fill the issue template.

License

Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.