本地访问VM中Docker部署的Kafka遇连接拒绝问题求助

一、本地生产者显示成功但无消息的核心原因及修复 #

1. 修正Kafka监听配置（关键） #

Kafka需要区分容器内部通信和外部（本地到VM）通信的监听地址，不能只配置VM静态IP。需在docker-compose.yml中调整Kafka的环境变量：

environment:
  KAFKA_LISTENERS: PLAINTEXT://0.0.0.0:9092,PLAINTEXT_HOST://0.0.0.0:9093
  KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:9092,PLAINTEXT_HOST://<你的VM静态IP>:9093
  KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT
  KAFKA_INTER_BROKER_LISTENER_NAME: PLAINTEXT

• PLAINTEXT://kafka:9092：供Docker容器内部（如Schema Registry、Kafka UI）访问
• PLAINTEXT_HOST://<VM_IP>:9093：供本地机器访问
• 同时在Kafka的ports字段添加外部端口映射："9093:9093"

2. 验证端口与网络连通性 #

• 确认VM的防火墙/安全组已开放9093端口（包括VM内部iptables和云服务商安全组，若为云VM）
• 本地执行telnet <VM_IP> 9093或nc -zv <VM_IP> 9093，确保端口能连通
• 本地生产者必须指定bootstrap.servers为<VM_IP>:9093，而非127.0.0.1

3. 检查Kafka日志排查连接问题 #

查看Kafka容器日志：

docker-compose logs kafka

如果出现Connection to node -1 (<VM_IP>:9093) could not be established类错误，说明端口未开放或IP配置错误。

二、Kafka UI无法解析schema-registry的修复 #

1. 确保所有服务在同一Docker网络 #

在docker-compose.yml中定义自定义网络，并让所有服务加入该网络：

networks:
  kafka-network:
    driver: bridge

services:
  zookeeper:
    # ...其他配置
    networks:
      - kafka-network
  kafka:
    # ...其他配置
    networks:
      - kafka-network
  schema-registry:
    # ...其他配置
    networks:
      - kafka-network
  kafka-ui:
    # ...其他配置
    networks:
      - kafka-network

同一网络下，容器可通过服务名（如schema-registry）互相解析。

2. 修正Kafka UI的Schema Registry配置 #

在Kafka UI的环境变量中明确指定Schema Registry地址：

environment:
  KAFKA_CLUSTERS_0_SCHEMAREGISTRY: http://schema-registry:8081

3. 验证Schema Registry状态 #

先确认Schema Registry容器正常启动：

docker-compose logs schema-registry

若日志中出现Server started, listening for requests，说明服务正常；若出现连接Kafka失败的错误，检查Schema Registry的SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS配置是否为PLAINTEXT://kafka:9092（容器内部地址）。

完整示例docker-compose.yml #

version: '3.8'
networks:
  kafka-network:
    driver: bridge

services:
  zookeeper:
    image: confluentinc/cp-zookeeper:latest
    environment:
      ZOOKEEPER_CLIENT_PORT: 2181
      ZOOKEEPER_TICK_TIME: 2000
    networks:
      - kafka-network

  kafka:
    image: confluentinc/cp-kafka:latest
    depends_on:
      - zookeeper
    ports:
      - "9093:9093"
    environment:
      KAFKA_BROKER_ID: 1
      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
      KAFKA_LISTENERS: PLAINTEXT://0.0.0.0:9092,PLAINTEXT_HOST://0.0.0.0:9093
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:9092,PLAINTEXT_HOST://192.168.1.100:9093  # 替换为你的VM静态IP
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT
      KAFKA_INTER_BROKER_LISTENER_NAME: PLAINTEXT
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
    networks:
      - kafka-network

  schema-registry:
    image: confluentinc/cp-schema-registry:latest
    depends_on:
      - kafka
    ports:
      - "8081:8081"
    environment:
      SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS: PLAINTEXT://kafka:9092
      SCHEMA_REGISTRY_HOST_NAME: schema-registry
      SCHEMA_REGISTRY_LISTENERS: http://0.0.0.0:8081
    networks:
      - kafka-network

  kafka-ui:
    image: provectuslabs/kafka-ui:latest
    depends_on:
      - kafka
      - schema-registry
    ports:
      - "8080:8080"
    environment:
      KAFKA_CLUSTERS_0_NAME: local-cluster
      KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: kafka:9092
      KAFKA_CLUSTERS_0_SCHEMAREGISTRY: http://schema-registry:8081
    networks:
      - kafka-network

最后操作步骤 #

1. 替换示例中的<VM静态IP>为实际IP
2. 清理旧容器并重启：

docker-compose down -v && docker-compose up -d

3. 本地生产者测试时，务必使用VM_IP:9093作为bootstrap地址

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