In order to unify the approaches followed for Bitnami containers and Bitnami Helm charts, we are moving the different bitnami/bitnami-docker-<container> repositories to a single monorepo bitnami/containers. Please follow bitnami/containers to keep you updated about the latest Bitnami images.
More information here: https://blog.bitnami.com/2022/07/new-source-of-truth-bitnami-containers.html
Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.
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.
The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-kafka/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- 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.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
- All Bitnami images available in Docker Hub are signed with Docker Content Trust (DCT). You can use
DOCKER_CONTENT_TRUST=1to verify the integrity of the images. - Bitnami container images are released on a regular basis with the latest distribution packages available.
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 Apache Kafka Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
3.2,3.2-debian-11,3.2.0,3.2.0-debian-11-r19,latest(3.2/debian-11/Dockerfile)3.1,3.1-debian-11,3.1.1,3.1.1-debian-11-r20(3.1/debian-11/Dockerfile)3.0,3.0-debian-11,3.0.1,3.0.1-debian-11-r19(3.0/debian-11/Dockerfile)
Subscribe to project updates by watching the bitnami/kafka GitHub repo.
The recommended way to get the Bitnami Apache Kafka Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/kafka:latestTo 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/kafka:[TAG]If you wish, you can also build the image yourself.
docker build -t bitnami/kafka:latest 'https://github.com/bitnami/bitnami-docker-kafka.git#master:3.2/debian-11'If you remove the container all your data and configurations 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.
Note: If you have already started using your database, follow the steps on backing up and restoring to pull the data from your running container down to your host.
The image exposes a volume at /bitnami/kafka for the Apache Kafka data. For persistence you can mount a directory at this location from your host. If the mounted directory is empty, it will be initialized on the first run.
Using Docker Compose:
This requires a minor change to the docker-compose.yml file present in this repository:
kafka:
...
volumes:
- /path/to/kafka-persistence:/bitnami/kafka
...NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001.
Using Docker container networking, a Apache Kafka server running inside a container can easily be accessed by your application containers.
Containers attached to the same network can communicate with each other using the container name as the hostname.
In this example, we will create a Apache Kafka client instance that will connect to the server instance that is running on the same docker network as the client.
$ docker network create app-tier --driver bridgeUse the --network app-tier argument to the docker run command to attach the Zookeeper container to the app-tier network.
$ docker run -d --name zookeeper-server \
--network app-tier \
-e ALLOW_ANONYMOUS_LOGIN=yes \
bitnami/zookeeper:latestUse the --network app-tier argument to the docker run command to attach the Apache Kafka container to the app-tier network.
$ docker run -d --name kafka-server \
--network app-tier \
-e ALLOW_PLAINTEXT_LISTENER=yes \
-e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper-server:2181 \
bitnami/kafka:latestFinally we create a new container instance to launch the Apache Kafka client and connect to the server created in the previous step:
$ docker run -it --rm \
--network app-tier \
-e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper-server:2181 \
bitnami/kafka:latest kafka-topics.sh --list --bootstrap-server kafka-server:9092When 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 app-tier. In this example we assume that you want to connect to the Apache Kafka server from your own custom application image which is identified in the following snippet by the service name myapp.
version: '2'
networks:
app-tier:
driver: bridge
services:
zookeeper:
image: 'bitnami/zookeeper:latest'
networks:
- app-tier
kafka:
image: 'bitnami/kafka:latest'
networks:
- app-tier
myapp:
image: 'YOUR_APPLICATION_IMAGE'
networks:
- app-tierIMPORTANT:
- Please update the
YOUR_APPLICATION_IMAGEplaceholder in the above snippet with your application image- Configure Apache Kafka and ZooKeeper persistence, and configure them either via environment variables or by mounting configuration files.
- In your application container, use the hostname
kafkato connect to the Apache Kafka server
Launch the containers using:
$ docker-compose up -dThe configuration can easily be setup with the Bitnami Apache Kafka Docker image using the following environment variables:
ALLOW_PLAINTEXT_LISTENER: Allow to use the PLAINTEXT listener. Default: no.KAFKA_INTER_BROKER_USER: Apache Kafka inter broker communication user. Default: admin. Default: user.KAFKA_INTER_BROKER_PASSWORD: Apache Kafka inter broker communication password. Default: bitnami.KAFKA_CERTIFICATE_PASSWORD: Password for certificates. No defaults.KAFKA_HEAP_OPTS: Apache Kafka's Java Heap size. Default: -Xmx1024m -Xms1024m.KAFKA_ZOOKEEPER_PROTOCOL: Authentication protocol for Zookeeper connections. Allowed protocols: PLAINTEXT, SASL, SSL, and SASL_SSL. Defaults: PLAINTEXT.KAFKA_ZOOKEEPER_USER: Apache Kafka Zookeeper user for SASL authentication. No defaults.KAFKA_ZOOKEEPER_PASSWORD: Apache Kafka Zookeeper user password for SASL authentication. No defaults.KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD: Apache Kafka Zookeeper keystore file password and key password. No defaults.KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD: Apache Kafka Zookeeper truststore file password. No defaults.KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME: Verify Zookeeper hostname on TLS certificates. Defaults: true.KAFKA_ZOOKEEPER_TLS_TYPE: Choose the TLS certificate format to use. Allowed values:JKS,PEM. Defaults: JKS.KAFKA_CFG_SASL_ENABLED_MECHANISMS: Allowed mechanism when using SASL either for clients, inter broker, or zookeeper comunications. Allowed values:PLAIN,SCRAM-SHA-256,SCRAM-SHA-512or a comma separated combination of those values. Default: PLAIN,SCRAM-SHA-256,SCRAM-SHA-512KAFKA_CFG_SASL_MECHANISM_INTER_BROKER_PROTOCOL: SASL mechanism to use for inter broker communications. No defaults.KAFKA_TLS_CLIENT_AUTH: Configures kafka brokers to request client authentication. Allowed values:required,requested,none. Defaults: required.KAFKA_TLS_TYPE: Choose the TLS certificate format to use. Allowed values:JKS,PEM. Defaults: JKS.KAFKA_CLIENT_USERS: Users that will be created into Zookeeper when using SASL for client communications. Separated by commas. Default: userKAFKA_CLIENT_PASSWORDS: Passwords for the users specified atKAFKA_CLIENT_USERS. Separated by commas. Default: bitnamiKAFKA_CFG_MAX_PARTITION_FETCH_BYTES: The maximum amount of data per-partition the server will return. Default: 1048576KAFKA_CFG_MAX_REQUEST_SIZE: The maximum size of a request in bytes. Default: 1048576KAFKA_ENABLE_KRAFT: Whether to enable Kafka Raft (KRaft) mode. Default: noKAFKA_KRAFT_CLUSTER_ID: Kafka cluster ID when using Kafka Raft (KRaft). No defaults.
Additionally, any environment variable beginning with KAFKA_CFG_ will be mapped to its corresponding Apache Kafka key. For example, use KAFKA_CFG_BACKGROUND_THREADS in order to set background.threads or KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE in order to configure auto.create.topics.enable.
$ docker run --name kafka -e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181 -e ALLOW_PLAINTEXT_LISTENER=yes -e KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE=true bitnami/kafka:latestor by modifying the docker-compose.yml file present in this repository:
kafka:
...
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
...To use Apache Kafka in a development setup, create the following docker-compose.yml file:
version: "3"
services:
zookeeper:
image: 'bitnami/zookeeper:latest'
ports:
- '2181:2181'
environment:
- ALLOW_ANONYMOUS_LOGIN=yes
kafka:
image: 'bitnami/kafka:latest'
ports:
- '9092:9092'
environment:
- KAFKA_BROKER_ID=1
- KAFKA_CFG_LISTENERS=PLAINTEXT://:9092
- KAFKA_CFG_ADVERTISED_LISTENERS=PLAINTEXT://127.0.0.1:9092
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
depends_on:
- zookeeperTo deploy it, run the following command in the directory where the docker-compose.yml file is located:
docker-compose up -d
Apache Kafka Raft (KRaft) makes use of a new quorum controller service in Kafka which replaces the previous controller and makes use of an event-based variant of the Raft consensus protocol. This greatly simplifies Kafka’s architecture by consolidating responsibility for metadata into Kafka itself, rather than splitting it between two different systems: ZooKeeper and Kafka.
More Info can be found here: https://developer.confluent.io/learn/kraft/
NOTE: KRaft is in early access and should be used in development only. It is not suitable for production.
Configuration here has been crafted from the Kraft Repo.
version: "3"
services:
- zookeeper:
- image: 'bitnami/zookeeper:latest'
- ports:
- - '2181:2181'
- environment:
- - ALLOW_ANONYMOUS_LOGIN=yes
kafka:
image: 'bitnami/kafka:latest'
ports:
- '9092:9092'
environment:
+ - KAFKA_ENABLE_KRAFT=yes
+ - KAFKA_CFG_PROCESS_ROLES=broker,controller
+ - KAFKA_CFG_CONTROLLER_LISTENER_NAMES=CONTROLLER
- - KAFKA_CFG_LISTENERS=PLAINTEXT://:9092
+ - KAFKA_CFG_LISTENERS=PLAINTEXT://:9092,CONTROLLER://:9093
+ - KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAP=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT
- KAFKA_CFG_ADVERTISED_LISTENERS=PLAINTEXT://127.0.0.1:9092
- KAFKA_BROKER_ID=1
+ - [email protected]:9093
- - KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
- depends_on:
- - zookeeperIn order to use internal and external clients to access Apache Kafka brokers you need to configure one listener for each kind of clients.
To do so, add the following environment variables to your docker-compose:
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
+ - KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAP=CLIENT:PLAINTEXT,EXTERNAL:PLAINTEXT
+ - KAFKA_CFG_LISTENERS=CLIENT://:9092,EXTERNAL://:9093
+ - KAFKA_CFG_ADVERTISED_LISTENERS=CLIENT://kafka:9092,EXTERNAL://localhost:9093
+ - KAFKA_CFG_INTER_BROKER_LISTENER_NAME=CLIENTAnd expose the external port:
(the internal, client one can still be used within the docker network)
ports:
- - '9092:9092'
+ - '9093:9093'Note: To connect from an external machine, change localhost above to your host's external IP/hostname and include EXTERNAL://0.0.0.0:9093 in KAFKA_CFG_LISTENERS to allow for remote connections.
These clients, from the same host, will use localhost to connect to Apache Kafka.
kafka-console-producer.sh --broker-list 127.0.0.1:9093 --topic test
kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9093 --topic test --from-beginningIf running these commands from another machine, change the address accordingly.
These clients, from other containers on the same Docker network, will use the kafka container service hostname to connect to Apache Kafka.
kafka-console-producer.sh --broker-list kafka:9092 --topic test
kafka-console-consumer.sh --bootstrap-server kafka:9092 --topic test --from-beginningSimilarly, application code will need to use bootstrap.servers=kafka:9092
More info about Apache Kafka listeners can be found in this great article
The Bitnami Apache Kafka docker image disables the PLAINTEXT listener for security reasons. You can enable the PLAINTEXT listener by adding the next environment variable, but remember that this configuration is not recommended for production.
ALLOW_PLAINTEXT_LISTENER=yesIn order to configure authentication, you must configure the Apache Kafka listeners properly. This container assumes the names below will be used for the listeners:
- INTERNAL: used for inter-broker communications.
- CLIENT: used for communications with clients that are within the same network as Apache Kafka brokers.
Let's see an example to configure Apache Kafka with SASL_SSL authentication for communications with clients, and SSL authentication for inter-broker communication.
The environment variables below should be define to configure the listeners, and the SASL credentials for client communications:
KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAP=INTERNAL:SSL,CLIENT:SASL_SSL
KAFKA_CFG_LISTENERS=INTERNAL://:9093,CLIENT://:9092
KAFKA_CFG_ADVERTISED_LISTENERS=INTERNAL://kafka:9093,CLIENT://kafka:9092
KAFKA_CFG_INTER_BROKER_LISTENER_NAME=INTERNAL
KAFKA_CLIENT_USERS=user
KAFKA_CLIENT_PASSWORDS=passwordYou must also use your own certificates for SSL. You can drop your Java Key Stores or PEM files into /opt/bitnami/kafka/config/certs. If the JKS or PEM certs are password protected (recommended), you will need to provide it to get access to the keystores:
KAFKA_CERTIFICATE_PASSWORD=myCertificatePassword
If the truststore is mounted in a different location than /opt/bitnami/kafka/config/certs/kafka.truststore.jks, /opt/bitnami/kafka/conf/certs/kafka.truststore.pem, /bitnami/kafka/conf/certs/kafka.truststore.jks or /bitnami/kafka/conf/certs/kafka.truststore.pem, set the KAFKA_TLS_TRUSTSTORE_FILE variable.
The following script can help you with the creation of the JKS and certificates:
Keep in mind the following notes:
- When prompted to enter a password, use the same one for all.
- Set the Common Name or FQDN values to your Apache Kafka container hostname, e.g.
kafka.example.com. After entering this value, when prompted "What is your first and last name?", enter this value as well.- As an alternative, you can disable host name verification setting the environment variable
KAFKA_CFG_SSL_ENDPOINT_IDENTIFICATION_ALGORITHMto an empty string.
- As an alternative, you can disable host name verification setting the environment variable
- When setting up a Apache Kafka Cluster (check this section for more information), each Apache Kafka broker and logical client needs its own keystore. You will have to repeat the process for each of the brokers in the cluster.
The following docker-compose file is an example showing how to mount your JKS certificates protected by the password certificatePassword123. Additionally it is specifying the Apache Kafka container hostname and the credentials for the client and zookeeper users.
version: '2'
services:
zookeeper:
image: 'bitnami/zookeeper:latest'
ports:
- '2181:2181'
environment:
- ZOO_ENABLE_AUTH=yes
- ZOO_SERVER_USERS=kafka
- ZOO_SERVER_PASSWORDS=kafka_password
kafka:
image: 'bitnami/kafka:latest'
hostname: kafka.example.com
ports:
- '9092'
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- KAFKA_CFG_LISTENERS=SASL_SSL://:9092
- KAFKA_CFG_ADVERTISED_LISTENERS=SASL_SSL://:9092
- KAFKA_ZOOKEEPER_USER=kafka
- KAFKA_ZOOKEEPER_PASSWORD=kafka_password
- KAFKA_CLIENT_USERS=user
- KAFKA_CLIENT_PASSWORDS=password
- KAFKA_CERTIFICATE_PASSWORD=certificatePassword123
- KAFKA_TLS_TYPE=JKS # or PEM
volumes:
# Both .jks and .pem files are supported
# - './kafka.keystore.pem:/opt/bitnami/kafka/config/certs/kafka.keystore.pem:ro'
# - './kafka.keystore.key:/opt/bitnami/kafka/config/certs/kafka.keystore.key:ro'
# - './kafka.truststore.pem:/opt/bitnami/kafka/config/certs/kafka.truststore.pem:ro'
- './kafka.keystore.jks:/opt/bitnami/kafka/config/certs/kafka.keystore.jks:ro'
- './kafka.truststore.jks:/opt/bitnami/kafka/config/certs/kafka.truststore.jks:ro'In order to get the required credentials to consume and produce messages you need to provide the credentials in the client. If your Apache Kafka client allows it, use the credentials you've provided.
While producing and consuming messages using the bitnami/kafka image, you'll need to point to the consumer.properties and/or producer.properties file, which contains the needed configuration
to work. You can find this files in the /opt/bitnami/kafka/conf directory.
Use this to generate messages using a secure setup:
export KAFKA_OPTS="-Djava.security.auth.login.config=/opt/bitnami/kafka/conf/kafka_jaas.conf"
kafka-console-producer.sh --broker-list 127.0.0.1:9092 --topic test --producer.config /opt/bitnami/kafka/conf/producer.propertiesUse this to consume messages using a secure setup
export KAFKA_OPTS="-Djava.security.auth.login.config=/opt/bitnami/kafka/conf/kafka_jaas.conf"
kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 --topic test --consumer.config /opt/bitnami/kafka/conf/consumer.propertiesIf you use other tools to use your Apache Kafka cluster, you'll need to provide the required information. You can find the required information in the files located at /opt/bitnami/kafka/conf directory.
When configuring your broker to use SASL or SASL_SSL for inter-broker communications, you can provide the SASL credentials using these environment variables:
KAFKA_INTER_BROKER_USER: Apache Kafka inter broker communication user. Deprecated in favor ofKAFKA_CLIENT_USERS.KAFKA_INTER_BROKER_PASSWORD: Apache Kafka inter broker communication password. Deprecated in favor ofKAFKA_CLIENT_PASSWORDS.
When configuring Apache Kafka with SASL or SASL_SSL for communications with clients, you can provide your the SASL credentials using this environment variables:
KAFKA_CLIENT_USERS: Apache Kafka client user. Default: userKAFKA_CLIENT_PASSWORDS: Apache Kafka client user password. Default: bitnami
There are different options of configuration to connect a Zookeeper server.
In order to connect a Zookeeper server without authentication, you should provide the environment variables below:
KAFKA_ZOOKEEPER_PROTOCOL: PLAINTEXT.
In order to authenticate Apache Kafka against a Zookeeper server with SASL, you should provide the environment variables below:
KAFKA_ZOOKEEPER_PROTOCOL: SASL.KAFKA_ZOOKEEPER_USER: Apache Kafka Zookeeper user for SASL authentication. No defaults.KAFKA_ZOOKEEPER_PASSWORD: Apache Kafka Zookeeper user password for SASL authentication. No defaults.
In order to authenticate Apache Kafka against a Zookeeper server with SSL, you should provide the environment variables below:
KAFKA_ZOOKEEPER_PROTOCOL: SSL.KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD: Apache Kafka Zookeeper keystore file password and key password. No defaults.KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD: Apache Kafka Zookeeper truststore file password. No defaults.KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME: Verify Zookeeper hostname on TLS certificates. Defaults: true.KAFKA_ZOOKEEPER_TLS_TYPE: Choose the TLS certificate format to use. Allowed values:JKS,PEM. Defaults: JKS.
In order to authenticate Apache Kafka against a Zookeeper server with SASL_SSL, you should provide the environment variables below:
KAFKA_ZOOKEEPER_PROTOCOL: SASL_SSL.KAFKA_ZOOKEEPER_USER: Apache Kafka Zookeeper user for SASL authentication. No defaults.KAFKA_ZOOKEEPER_PASSWORD: Apache Kafka Zookeeper user password for SASL authentication. No defaults.KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_FILE: Apache Kafka Zookeeper truststore file location. Set it if the mount location is different from/bitnami/kafka/conf/certs/zookeeper.truststore.pem,/bitnami/kafka/conf/certs/zookeeper.truststore.jks,/opt/bitnami/kafka/config/certs/zookeeper.truststore.jksor/opt/bitnami/kafka/conf/certs/zookeeper.truststore.pemNo defaults.KAFKA_ZOOKEEPER_TLS_KEYSTORE_PASSWORD: Apache Kafka Zookeeper keystore file password and key password. No defaults.KAFKA_ZOOKEEPER_TLS_TRUSTSTORE_PASSWORD: Apache Kafka Zookeeper truststore file password. No defaults.KAFKA_ZOOKEEPER_TLS_VERIFY_HOSTNAME: Verify Zookeeper hostname on TLS certificates. Defaults: true.KAFKA_ZOOKEEPER_TLS_TYPE: Choose the TLS certificate format to use. Allowed values:JKS,PEM. Defaults: JKS.
Note: You must also use your own certificates for SSL. You can mount your Java Key Stores (
zookeeper.keystore.jksandzookeeper.truststore.jks) or PEM files (zookeeper.keystore.pem,zookeeper.keystore.keyandzookeeper.truststore.pem) into/opt/bitnami/kafka/conf/certs. If client authentication isnoneorwantin Zookeeper, the cert files are optional.
A Apache Kafka cluster can easily be setup with the Bitnami Apache Kafka Docker image using the following environment variables:
KAFKA_CFG_ZOOKEEPER_CONNECT: Comma separated host:port pairs, each corresponding to a Zookeeper Server.
Create a Docker network to enable visibility to each other via the docker container name
$ docker network create app-tier --driver bridgeThe first step is to create one Zookeeper instance.
$ docker run --name zookeeper \
--network app-tier \
-e ALLOW_ANONYMOUS_LOGIN=yes \
-p 2181:2181 \
bitnami/zookeeper:latestThe first step is to create one Apache Kafka instance.
$ docker run --name kafka1 \
--network app-tier \
-e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181 \
-e ALLOW_PLAINTEXT_LISTENER=yes \
-p :9092 \
bitnami/kafka:latestNext we start a new Apache Kafka container.
$ docker run --name kafka2 \
--network app-tier \
-e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181 \
-e ALLOW_PLAINTEXT_LISTENER=yes \
-p :9092 \
bitnami/kafka:latestNext we start another new Apache Kafka container.
$ docker run --name kafka3 \
--network app-tier \
-e KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181 \
-e ALLOW_PLAINTEXT_LISTENER=yes \
-p :9092 \
bitnami/kafka:latestYou now have a Apache Kafka cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime.
With Docker Compose, topic replication can be setup using:
version: '2'
services:
zookeeper:
image: 'bitnami/zookeeper:latest'
ports:
- '2181:2181'
environment:
- ALLOW_ANONYMOUS_LOGIN=yes
kafka1:
image: 'bitnami/kafka:latest'
ports:
- '9092'
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
kafka2:
image: 'bitnami/kafka:latest'
ports:
- '9092'
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
kafka3:
image: 'bitnami/kafka:latest'
ports:
- '9092'
environment:
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yesThen, you can create a replicated topic with:
root@kafka1:/# /opt/bitnami/kafka/bin/kafka-topics.sh --create --bootstrap-server localhost:9092 --topic mytopic --partitions 3 --replication-factor 3
Created topic "mytopic".
root@kafka1:/# /opt/bitnami/kafka/bin/kafka-topics.sh --describe --bootstrap-server localhost:9092 --topic mytopic
Topic:mytopic PartitionCount:3 ReplicationFactor:3 Configs:
Topic: mytopic Partition: 0 Leader: 2 Replicas: 2,3,1 Isr: 2,3,1
Topic: mytopic Partition: 1 Leader: 3 Replicas: 3,1,2 Isr: 3,1,2
Topic: mytopic Partition: 2 Leader: 1 Replicas: 1,2,3 Isr: 1,2,3The image looks for configuration files (server.properties, log4j.properties, etc.) in the /bitnami/kafka/config/ directory, this directory can be changed by setting the KAFKA_MOUNTED_CONF_DIR environment variable.
$ docker run --name kafka -v /path/to/server.properties:/bitnami/kafka/config/server.properties bitnami/kafka:latestAfter that, your changes will be taken into account in the server's behaviour.
Run the Apache Kafka image, mounting a directory from your host.
Modify the docker-compose.yml file present in this repository:
...
services:
kafka:
...
volumes:
- 'kafka_data:/bitnami'
+ - /path/to/server.properties:/bitnami/kafka/config/server.propertiesEdit the configuration on your host using your favorite editor.
vi /path/to/server.propertiesAfter changing the configuration, restart your Apache Kafka container for changes to take effect.
$ docker restart kafkaOr using Docker Compose:
$ docker-compose restart kafkaThe Bitnami Apache Kafka Docker image sends the container logs to the stdout. To view the logs:
$ docker logs kafkaOr using Docker Compose:
$ docker-compose logs kafkaYou can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.
To backup your data, configuration and logs, follow these simple steps:
$ docker stop kafkaOr using Docker Compose:
$ docker-compose stop kafkaWe need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
$ docker run --rm -v /path/to/kafka-backups:/backups --volumes-from kafka busybox \
cp -a /bitnami/kafka:latest /backups/latestOr using Docker Compose:
$ docker run --rm -v /path/to/kafka-backups:/backups --volumes-from `docker-compose ps -q kafka` busybox \
cp -a /bitnami/kafka:latest /backups/latestRestoring a backup is as simple as mounting the backup as volumes in the container.
$ docker run -v /path/to/kafka-backups/latest:/bitnami/kafka bitnami/kafka:latestYou can also modify the docker-compose.yml file present in this repository:
kafka:
volumes:
- /path/to/kafka-backups/latest:/bitnami/kafkaBitnami provides up-to-date versions of Apache Kafka, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
$ docker pull bitnami/kafka:latestor if you're using Docker Compose, update the value of the image property to
bitnami/kafka:latest.
Before continuing, you should backup your container's data, configuration and logs.
Follow the steps on creating a backup.
$ docker rm -v kafkaOr using Docker Compose:
$ docker-compose rm -v kafkaRe-create your container from the new image, restoring your backup if necessary.
$ docker run --name kafka bitnami/kafka:latestOr using Docker Compose:
$ docker-compose up kafkaBranch 2 has been renamed to 2.8 and branch 3 has been splited into branches 3.0 and 3.1 mirroing the upstream Apache Kafka's naming policy
- Apache Kafka 3.0 deprecates the
--zookeperflag in shell commands. Related operations such as topic creation require the use of updated flags. Please, refer to Apache Kafka's official release notes for further information on the changes introduced by this version.
- The
KAFKA_CLIENT_USERANDKAFKA_CLIENT_PASSWORDhave been deprecated in favor ofKAFKA_CLIENT_USERSandKAFKA_CLIENT_PASSWORDS.
-
The environment variables
KAFKA_PORT_NUMBERandKAFKA_CFG_PORTwas deprecated, you can specify the port number inKAFKA_CFG_LISTENERSinstead. -
The following environment variables were renamed:
KAFKA_BROKER_USER->KAFKA_CLIENT_USERKAFKA_BROKER_PASSWORD->KAFKA_CLIENT_PASSWORD
-
Listeners & advertised listeners must be configured to enable authentication. Check Security section for more information.
The configuration directory was changed to /opt/bitnami/kafka/config. Configuration files should be mounted to /bitnami/kafka/config.
-
The following environment variables were beingly wrongly translated into
KAFKA_CFG_environment variables, and therefore they were being wrongly mapped into Apache Kafka keys:KAFKA_LOGS_DIRS->KAFKA_CFG_LOG_DIRSKAFKA_PORT_NUMBER->KAFKA_CFG_PORTKAFKA_ZOOKEEPER_CONNECT_TIMEOUT_MS->KAFKA_CFG_ZOOKEEPER_CONNECTION_TIMEOUT_MS
-
For consistency reasons with previous environment variables, the following
KAFKA_toKAFKA_CFG_environment variable translations are now supported for mapping into Apache Kafka keys:KAFKA_LOG_DIRS->KAFKA_CFG_LOG_DIRSKAFKA_ZOOKEEPER_CONNECTION_TIMEOUT_MS->KAFKA_CFG_ZOOKEEPER_CONNECTION_TIMEOUT_MS
Configuration changes. Most environment variables now start with KAFKA_CFG_, as they are now mapped directly to Apache Kafka keys. Variables changed:
KAFKA_ADVERTISED_LISTENERS->KAFKA_CFG_ADVERTISED_LISTENERSKAFKA_BROKER_ID->KAFKA_CFG_BROKER_IDKAFKA_DEFAULT_REPLICATION_FACTOR->KAFKA_CFG_DEFAULT_REPLICATION_FACTORKAFKA_DELETE_TOPIC_ENABLE->KAFKA_CFG_DELETE_TOPIC_ENABLEKAFKA_INTER_BROKER_LISTENER_NAME->KAFKA_CFG_INTER_BROKER_LISTENER_NAMEKAFKA_LISTENERS->KAFKA_CFG_LISTENERSKAFKA_LISTENER_SECURITY_PROTOCOL_MAP->KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAPKAFKA_LOGS_DIRS->KAFKA_CFG_LOG_DIRSKAFKA_LOG_FLUSH_INTERVAL_MESSAGES->KAFKA_CFG_LOG_FLUSH_INTERVAL_MESSAGESKAFKA_LOG_FLUSH_INTERVAL_MS->KAFKA_CFG_LOG_FLUSH_INTERVAL_MSKAFKA_LOG_MESSAGE_FORMAT_VERSION->KAFKA_CFG_LOG_MESSAGE_FORMAT_VERSIONKAFKA_LOG_RETENTION_BYTES->KAFKA_CFG_LOG_RETENTION_BYTESKAFKA_LOG_RETENTION_CHECK_INTERVALS_MS->KAFKA_CFG_LOG_RETENTION_CHECK_INTERVAL_MSKAFKA_LOG_RETENTION_HOURS->KAFKA_CFG_LOG_RETENTION_HOURSKAFKA_MAX_MESSAGE_BYTES->KAFKA_CFG_MESSAGE_MAX_BYTESKAFKA_NUM_IO_THREADS->KAFKA_CFG_NUM_IO_THREADSKAFKA_NUM_NETWORK_THREADS->KAFKA_CFG_NUM_NETWORK_THREADSKAFKA_NUM_PARTITIONS->KAFKA_CFG_NUM_PARTITIONSKAFKA_NUM_RECOVERY_THREADS_PER_DATA_DIR->KAFKA_CFG_NUM_RECOVERY_THREADS_PER_DATA_DIRKAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR->KAFKA_CFG_OFFSETS_TOPIC_REPLICATION_FACTORKAFKA_PORT->KAFKA_CFG_PORTKAFKA_SEGMENT_BYTES->KAFKA_CFG_SEGMENT_BYTESKAFKA_SOCKET_RECEIVE_BUFFER_BYTES->KAFKA_CFG_SOCKET_RECEIVE_BUFFER_BYTESKAFKA_SOCKET_REQUEST_MAX_BYTES->KAFKA_CFG_SOCKET_REQUEST_MAX_BYTESKAFKA_SOCKET_SEND_BUFFER_BYTES->KAFKA_CFG_SOCKET_SEND_BUFFER_BYTESKAFKA_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM->KAFKA_CFG_SSL_ENDPOINT_IDENTIFICATION_ALGORITHMKAFKA_TRANSACTION_STATE_LOG_MIN_ISR->KAFKA_CFG_TRANSACTION_STATE_LOG_MIN_ISRKAFKA_TRANSACTION_STATE_LOG_REPLICATION_FACTOR->KAFKA_CFG_TRANSACTION_STATE_LOG_REPLICATION_FACTORKAFKA_ZOOKEEPER_CONNECT_TIMEOUT_MS->KAFKA_CFG_ZOOKEEPER_CONNECT_TIMEOUT_MSKAFKA_ZOOKEEPER_CONNECT->KAFKA_CFG_ZOOKEEPER_CONNECT
- Configuration is not persisted anymore. It should be mounted as a volume or it will be regenerated each time the container is created.
- Dummy certificates are not used anymore when the SASL_SSL listener is configured. These certificates must be mounted as volumes.
- The kafka container has been migrated to a non-root container approach. Previously the container run as
rootuser and the kafka daemon was started askafkauser. From now own, both the container and the kafka daemon run as user1001. As a consequence, the configuration files are writable by the user running the kafka process.
- New Bitnami release
We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version) - Output of
docker info - Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright © 2022 Bitnami
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.