nanjiek commented on issue #724: URL: https://github.com/apache/dubbo-go-pixiu/issues/724#issuecomment-3315987104
**English:** I have tested this scenario. Running Pixiu in Docker with `--network=host` and the backend server on Windows works fine. The root cause is that in WSL2 the server binds only to `127.0.0.1`, which is not accessible from Docker. To fix it, the server inside WSL2 must be reachable from outside WSL. One option is to bind to `0.0.0.0`, but that may expose the port to the whole network, which is unsafe in some environments. A safer choice is to: * Bind only to the WSL2 interface IP (e.g. `172.27.x.x`), or * Use Windows port forwarding to expose the port to `host.docker.internal`. In practice, three setups work: 1. **Server on Windows + Pixiu in Docker** → use `host.docker.internal:PORT`. 2. **Server also in Docker** → run both in the same Docker network and use the container name. 3. **Server in WSL2** → bind to the WSL IP (instead of only `127.0.0.1`), or forward the port to Windows, then access via `host.docker.internal:PORT`. --- **中文:** 我测试过这个场景：Pixiu 在 Docker 中用 `--network=host` 运行，后端服务在 Windows 上启动时没有问题。问题的根源是：在 WSL2 中如果服务只监听 `127.0.0.1`，Docker 容器是无法访问到的。 要解决，需要让 WSL2 中的服务能够被外部访问。虽然可以直接监听 `0.0.0.0`，但这样会对整个网络暴露端口，在某些环境下存在安全风险。更安全的做法是： * 只绑定到 WSL2 的内部 IP（如 `172.27.x.x`），或者 * 在 Windows 上做端口转发，把端口暴露到 `host.docker.internal`。 实际可行的三种运行方式： 1. **服务在 Windows + Pixiu 在 Docker** → 使用 `host.docker.internal:PORT`。 2. **服务也放到 Docker** → 两个容器放到同一网络，用容器名互访。 3. **服务在 WSL2** → 绑定到 WSL 的 IP（不要只用 `127.0.0.1`），或者通过 Windows 转发端口，再用 `host.docker.internal:PORT` 访问。 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
