Hey there, let's walk through the most common fixes for this issue — I've dealt with similar Docker-Kafka connectivity headaches before, so here's what to check step by step:

1. Verify Port Exposure & Network Connectivity #

First, make sure you're exposing Kafka's default port (9092) when running the container. If you didn't map this port, external systems can't reach your broker. Your run command should include:

docker run -p 9092:9092 [your-kafka-image-name]

Test if the port is accessible from your host machine with:

telnet localhost 9092
# Or using netcat
nc -zv localhost 9092

If this fails, double-check the container is running (docker ps) and that no other service is using port 9092 on your host.

2. Fix Kafka's listeners and advertised.listeners Configuration #

This is the #1 culprit for external connectivity issues with Kafka in Docker. The default server.properties doesn't account for container networking, so you need to update two key settings:

Update server.properties (or override via environment variables) #

• listeners: Tells Kafka which internal addresses to listen on. Set this to allow all interfaces inside the container:

  listeners=PLAINTEXT://0.0.0.0:9092
  

• advertised.listeners: Tells external producers/consumers what address to use to connect to Kafka. This must be your host machine's IP (or localhost for local testing) and the mapped port:

  advertised.listeners=PLAINTEXT://your-host-ip:9092
  

Alternative: Override via Docker run command #

Instead of modifying the server.properties in your image, you can pass these settings as environment variables when starting the container (Kafka 1.1.0 supports this if you adjust your Dockerfile to load them, or use a base image that handles env vars):

docker run -p 9092:9092 \
  -e KAFKA_LISTENERS=PLAINTEXT://0.0.0.0:9092 \
  -e KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://your-host-ip:9092 \
  -e KAFKA_ZOOKEEPER_CONNECT=zk-container-ip:2181 \
  [your-kafka-image-name]

3. Confirm Kafka is Registered with ZooKeeper #

Even though you updated zookeeper.connect, let's verify the broker is actually registered with ZK. Exec into your Kafka container:

docker exec -it [kafka-container-id] /bin/bash

Then run the ZK shell to check broker registration:

bin/zookeeper-shell.sh zk-container-ip:2181

Once in the shell, run this command to see registered brokers:

ls /brokers/ids

You should see a numeric ID (like [1]) — if not, double-check your zookeeper.connect value and ensure the ZK container is reachable from the Kafka container (use ping zk-container-ip inside the Kafka container to test).

4. Check External Producer Configuration #

Make sure your external producer is using the host machine's IP/localhost and port 9092 in its bootstrap.servers setting. For example, if using the console producer:

# On your host machine (not inside the container)
kafka-console-producer.sh --broker-list your-host-ip:9092 --topic test-topic

If you use the container's internal IP here, the producer won't be able to reach it from outside the Docker network.

5. Quick Dockerfile Optimization Tip #

Instead of copying the entire Kafka directory into your image, you could download Kafka directly in the Dockerfile to keep it clean, and add a step to pre-configure listeners:

FROM openjdk:8
WORKDIR /app
RUN wget https://archive.apache.org/dist/kafka/1.1.0/kafka_2.11-1.1.0.tgz && \
    tar -xzf kafka_2.11-1.1.0.tgz && \
    mv kafka_2.11-1.1.0/* /app && \
    rm kafka_2.11-1.1.0.tgz
# Pre-configure listeners (you can still override at runtime)
RUN sed -i 's/#listeners=PLAINTEXT:\/\/:9092/listeners=PLAINTEXT:\/\/0.0.0.0:9092/' config/server.properties
ENTRYPOINT ["bin/kafka-server-start.sh", "config/server.properties"]

Start with checking the advertised.listeners and port mapping — those are almost always the fix for this specific issue. Let me know if any of these steps resolve your problem!

内容的提问来源于stack exchange，提问作者Alan Gaytan