bitflicker64 opened a new pull request, #2963: URL: https://github.com/apache/hugegraph/pull/2963
## Purpose of the PR - close #2951 Update all Docker deployment documentation to reflect the bridge networking migration from PR #2952. The old docs referenced a dead directory, used wrong environment variable names, and had no guidance for Docker Desktop users on Mac/Windows. ## Main Changes - **Create `docker/README.md`** (new file) — comprehensive setup guide covering single-node and 3-node cluster, full `HG_*` env var reference tables for PD/Store/Server, port reference, health verification commands, troubleshooting (OOM, Raft, partitions), and a note about the temporary entrypoint mount workaround until updated images are published - **Fix `hugegraph-store/docs/deployment-guide.md`** — replace Docker Compose section that used completely wrong env var names (`GRPC_HOST`, `RAFT_ADDRESS`, `RAFT_PEERS`, `PD_ADDRESS`, `BACKEND`, `PD_PEERS`) with correct `HG_*` names; also fix K8s manifest env var names - **Fix 7 files pointing to dead `hugegraph-server/hugegraph-dist/docker/example/` directory** — update to point to `docker/` with correct file names (`docker-compose.yml`, `docker-compose-dev.yml`, `docker-compose-3pd-3store-3server.yml`) - **Add Docker bridge network notes** to `hugegraph-pd/docs/configuration.md`, `hugegraph-pd/README.md`, `hugegraph-pd/AGENTS.md` — clarify that `grpc.host` accepts container hostnames in bridge mode via `HG_PD_GRPC_HOST` - **Add distributed cluster section** to `hugegraph-server/hugegraph-dist/docker/README.md` - **Update `docker run` examples** in `hugegraph-pd/README.md` and `hugegraph-store/README.md` to use correct `HG_*` env var names ## Verifying these changes - [x] Trivial rework / code cleanup without any test coverage. (No Need) ## Does this PR potentially affect the following parts? - [ ] Dependencies - [ ] Modify configurations - [ ] The public API - [ ] Other affects - [x] Nope ## Documentation Status - [x] `Doc - Done` -- 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]
