leizhiyuan opened a new issue, #1196: URL: https://github.com/apache/rocketmq-dashboard/issues/1196
## Problem Local `docker compose` bootstrap (the flow documented in `deploy/` and the `deploy-rocketmq` skill) fails in two places on Docker Engine: 1. `deploy/rocketmq/docker-compose.yml` pins static IPs (`10.89.2.x`) for the RocketMQ cluster containers, but the default network declares no `ipam` subnet. `docker compose up` aborts with `user specified IP address is supported only when connecting to networks with user configured subnets`, so the NameServer + broker + proxy cluster cannot start. 2. `web/15-resolver.envsh` derives the nginx upstream resolver from the default gateway (`ip route`). That is only correct under podman. On Docker Engine the gateway IP runs no DNS server, so nginx cannot resolve the `rocketmq-server` upstream and every `/api/` request returns 502 (`rocketmq-server could not be resolved`, Operation timed out). The frontend then reports that it cannot verify the login status and spins forever. ## Scope Local development bootstrap only; no runtime/API behavior change. Covers the Studio web container resolver and the RocketMQ dev-cluster compose definition. ## Expected - `docker compose up` in `deploy/rocketmq` starts the cluster (subnet matches the pinned IPs). - The web nginx proxy resolves `rocketmq-server` on Docker Engine and `/api/auth/status` returns 200. - podman behaviour is preserved via the gateway fallback. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
