1Panel-dev / 1Panel-dev/1Panel

[Feature] Issues related to the RocketMQ Compose file and broker configuration files

Open
#10,729 2 comments 1 reaction 1 assignee View on GitHub

@wanghe-fit2cloud is already working on this.

Since Oct 23, 2025.

type: app-store
Dominant language
Go
Stars
37k
Forks
3.4k
Avg merge
9h 16m
Merged PRs (30d)
105

Description

1Panel Version

v2.0.12

Please describe your needs or suggestions for improvements

当下版本v2.0.12版本的RocketMQ的compose文件的配置是这样的

services:
  namesrv:
    image: apache/rocketmq:5.3.3
    container_name: ${CONTAINER_NAME}-rmqnamesrv
    ports:
      - ${PANEL_APP_PORT_NAMESERVER}:9876
    networks:
      - 1panel-network
    volumes:
      - ./data/namesrv/logs:/home/rocketmq/logs
    command: sh mqnamesrv
    labels:
      createdBy: "Apps"
  broker:
    image: apache/rocketmq:5.3.3
    container_name: ${CONTAINER_NAME}-rmqbroker
    links:
      - namesrv
    ports:
      - ${PANEL_APP_PORT_FASTLISTEN}:10909
      - ${PANEL_APP_PORT_LISTEN}:10911
      - ${PANEL_APP_PORT_HALISTEN}:10912
    networks:
      - 1panel-network
    environment:
      - NAMESRV_ADDR=namesrv:9876
    volumes:
      - ./data/broker/logs:/home/rocketmq/logs
      - ./data/broker/store:/home/rocketmq/store
      - ./data/broker/conf/broker.conf:/opt/rocketmq-5.2.0/conf/broker.conf
    command: sh mqbroker -c /opt/rocketmq-5.2.0/conf/broker.conf
    labels:
      createdBy: "Apps"
  proxy:
    image: apache/rocketmq:5.3.3
    container_name: ${CONTAINER_NAME}-rmqproxy
    links:
      - namesrv
      - broker
    depends_on:
      - broker
    ports:
      - ${PANEL_APP_PORT_REMOTINGLISTEN}:8080
      - ${PANEL_APP_PORT_GRPCSERVER}:8081
    networks:
      - 1panel-network
    restart: on-failure
    environment:
      - NAMESRV_ADDR=namesrv:9876
    volumes:
      - ./data/proxy/logs:/home/rocketmq/logs
      - ./data/proxy/conf/rmq-proxy.json:/opt/rocketmq-5.2.0/conf/rmq-proxy.json
    command: sh mqproxy -pc /opt/rocketmq-5.2.0/conf/rmq-proxy.json
    labels:
      createdBy: "Apps"
  dashboard:
    image: apacherocketmq/rocketmq-dashboard:latest
    container_name: ${CONTAINER_NAME}-rmqdashboard
    links:
      - namesrv
    depends_on:
      - namesrv
    ports:
      - ${PANEL_APP_PORT_HTTP}:8080
    networks:
      - 1panel-network
    restart: on-failure
    environment:
      - JAVA_OPTS=-Drocketmq.namesrv.addr=namesrv:9876
    labels:
      createdBy: "Apps"
networks:
  1panel-network:
    external: true

apacherocketmq/rocketmq-dashboard:latest 容器内部的端口并不是8080,而是8082

还有一个问题就是,rocketmq启动异常的问题或者说无法正常进行通讯的问题,因为配置文件缺失配置的原因

brokerClusterName = DefaultCluster
brokerName = broker-a
brokerId = 0
deleteWhen = 04
fileReservedTime = 48
brokerRole = ASYNC_MASTER
flushDiskType = ASYNC_FLUSH
Please describe the solution you suggest

关于第一个问题的解决方案就是将8080改为8082

这是修改的具体内容:

- ${PANEL_APP_PORT_HTTP}:8082

关于第二个问题的解决方案是添加一段配置,

brokerClusterName = DefaultCluster
brokerName = broker-a
brokerId = 0
deleteWhen = 04
fileReservedTime = 48
brokerRole = ASYNC_MASTER
flushDiskType = ASYNC_FLUSH
brokerIP1 = 192.168.245.129

这个配置文件是rocketmq/data/broker/conf/broker.conf

希望1panel官方能对这两个点做一下优化,例如说将compose.xml 的初始文件进行修改优化,将dashboard的8080改为8082,另外给broker的配置文件broker.conf中注入brokerIP1 配置,来保证RocketMQ容器正常运行

Additional Information

注意:192.168.245.129 并未固定端口,而是自身服务器的端口,也就是运行容器的服务器端口,是否能用本地端口来这点并未测试,但是关于Rocket容器无法正常启动的问题目前就是用这种方式解决的

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.