Description
[Description]
The documented GPU smoke test command uses the ubuntu base image:bash
docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi
However, the official Ubuntu image on Docker Hub does not include the nvidia-smi binary, so this command fails with nvidia-smi: not found even when GPUs are correctly configured. The example is therefore misleading as a validation step for GPU availability.
[Environment]
Device: spark (1.120.38)
Node.js: v20.20.1
npm: 10.8.2
Docker: Docker Engine 29.3.0
OpenShell CLI: 0.0.16
NemoClaw: v0.1.0 (cec1e4)
OpenClaw: 2026.3.11 (29dc654)
Note: Behavior reproducible with the official ubuntu image from Docker Hub.
[Steps to Reproduce]
-
On a DGX Spark host with NVIDIA runtime configured, run:bash
docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi -
Observe that the container starts but the command fails because
nvidia-smi is not found in the Ubuntu image. -
Confirm that a CUDA-based image works, for example:bash
docker run --rm --gpus all nvidia/cuda:12.2.0-base-ubuntu22.04 nvidia-smi
[Expected Result]
The documentation’s GPU smoke test should either:
-
Use an image that actually includes
nvidia-smi (for example nvidia/cuda:*‑base‑*), so the command can successfully validate GPU access, or -
Clearly state that
nvidia-smi is expected to run on the host, not inside a minimal Ubuntu container.
[Actual Result]
The documented command suggests that nvidia-smi will run inside the ubuntu container, but the binary is missing in that image, causing users to see nvidia-smi: command not found or similar error even when GPU setup is correct. This can lead to confusion and misdiagnosis of GPU configuration issues.
Steps to reproduce
No steps provided.
[NVB# 6033961]
[NVB#6033961]
Description
[Description]
The documented GPU smoke test command uses the
ubuntubase image:bashdocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smiHowever, the official Ubuntu image on Docker Hub does not include the
nvidia-smibinary, so this command fails withnvidia-smi: not foundeven when GPUs are correctly configured. The example is therefore misleading as a validation step for GPU availability.[Environment]
Device: spark (1.120.38)
Node.js: v20.20.1
npm: 10.8.2
Docker: Docker Engine 29.3.0
OpenShell CLI: 0.0.16
NemoClaw: v0.1.0 (cec1e4)
OpenClaw: 2026.3.11 (29dc654)
Note: Behavior reproducible with the official
ubuntuimage from Docker Hub.[Steps to Reproduce]
docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-sminvidia-smiis not found in the Ubuntu image.docker run --rm --gpus all nvidia/cuda:12.2.0-base-ubuntu22.04 nvidia-smi[Expected Result]
The documentation’s GPU smoke test should either:
nvidia-smi(for examplenvidia/cuda:*‑base‑*), so the command can successfully validate GPU access, ornvidia-smiis expected to run on the host, not inside a minimal Ubuntu container.[Actual Result]
The documented command suggests that
nvidia-smiwill run inside theubuntucontainer, but the binary is missing in that image, causing users to seenvidia-smi: command not foundor similar error even when GPU setup is correct. This can lead to confusion and misdiagnosis of GPU configuration issues.Steps to reproduce
No steps provided.
[NVB# 6033961]
[NVB#6033961]