树莓派4上容器化Kafka启动失败问题求助

问题根源 #

你遇到的exec /usr/local/bin/kafka-docker.sh: exec format error是典型的架构不兼容问题：常规Confluent、Wurstmeister等Kafka/Zookeeper镜像是为x86_64架构编译的，树莓派4的ARM64架构无法执行x86二进制文件，必须使用适配ARM64的镜像。

解决方案：使用ARM64兼容镜像 #

以下提供两种经过验证的适配方案，直接替换原docker-compose配置即可：

方案1：Bitnami多架构镜像（推荐）

Bitnami官方镜像原生支持ARM64，无需额外配置，生态完善：

version: '3'
services:
  zookeeper:
    image: bitnami/zookeeper:latest
    container_name: zookeeper
    environment:
      - ALLOW_ANONYMOUS_LOGIN=yes
      - ZOOKEEPER_CLIENT_PORT=2181
    ports:
      - "2181:2181"
  kafka:
    image: bitnami/kafka:latest
    container_name: kafka
    environment:
      - ALLOW_PLAINTEXT_LISTENER=yes
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper:2181
      - KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://kafka:9092,PLAINTEXT_HOST://localhost:9093
      - KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT
      - KAFKA_CREATE_TOPICS=mqtt-sensor-1:1:1
    depends_on:
      - zookeeper
    ports:
      - "9093:9093"
    restart: on-failure

关键说明：

• ALLOW_ANONYMOUS_LOGIN/ALLOW_PLAINTEXT_LISTENER为测试用配置，生产环境需启用认证
• KAFKA_ADVERTISED_LISTENERS区分容器内部和外部访问地址，避免连接失败
• KAFKA_CREATE_TOPICS格式为topic名:分区数:副本数，与Confluent镜像参数格式不同

方案2：Obsidian Dynamics ARM专属镜像

专为ARM架构优化的轻量镜像：

version: '3'
services:
  zookeeper:
    image: obsidiandynamics/zookeeper
    container_name: zookeeper
    environment:
      - ZOO_MY_ID=1
    ports:
      - "2181:2181"
  kafka:
    image: obsidiandynamics/kafka
    container_name: kafka
    environment:
      - KAFKA_LISTENERS=PLAINTEXT://:9092
      - KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://kafka:9092
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper:2181
      - KAFKA_CREATE_TOPICS=mqtt-sensor-1:1:1
    depends_on:
      - zookeeper
    restart: on-failure

验证步骤 #

1. 清理旧容器：docker-compose down
2. 拉取适配镜像：docker-compose pull
3. 启动服务：docker-compose up -d
4. 检查启动日志：docker-compose logs kafka

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