From afcfe91dfab69df17318190b96d326ccdb10cdf3 Mon Sep 17 00:00:00 2001 From: Li Wang Date: Mon, 14 Jul 2025 17:56:57 +0800 Subject: [PATCH] [Doc] Fix multi node doc (#1783) ### What this PR does / why we need it? ### Does this PR introduce _any_ user-facing change? Pin docker image to latest release ### How was this patch tested? - vLLM version: v0.9.2 - vLLM main: https://github.com/vllm-project/vllm/commit/1e9438e0b0f65f2a5cfbd522d35638e7264c8399 Signed-off-by: wangli --- docs/source/tutorials/multi_node.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/source/tutorials/multi_node.md b/docs/source/tutorials/multi_node.md index eebdfda..d3d9a03 100644 --- a/docs/source/tutorials/multi_node.md +++ b/docs/source/tutorials/multi_node.md @@ -56,9 +56,10 @@ hccn_tool -i 0 -ping -g address 10.20.0.20 ## Run with docker Assume you have two Atlas 800 A2(64G*8) nodes, and want to deploy the `deepseek-v3-w8a8` quantitative model across multi-node. -```shell -# Define the image and container name -export IMAGE=quay.io/ascend/vllm-ascend:main +```{code-block} bash + :substitutions: +# Update the vllm-ascend image +export IMAGE=m.daocloud.io/quay.io/ascend/vllm-ascend:|vllm_ascend_version| export NAME=vllm-ascend # Run the container using the defined variables