docs: clarify NVIDIA GPU access scope

[codewithdaniel1]

Description

Clarify the note about NVIDIA GPU access in the Docker Engine container documentation.

The previous wording said that NVIDIA GPUs can only be accessed by systems running a "single engine", but did not define what "single engine" means. This update reframes the note around the documented scope of the page: standalone Docker Engine containers on a single host.

Related issues or tickets

Closes #25685

Reviews

• Technical review
• Editorial review
• Product review

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	c248951
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/6a721eff3f600000086f6216
😎 Deploy Preview	https://deploy-preview-25690--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[dvdksn]

This changes the meaning of the callout entirely. Maybe that's what you intended but I'm not able to verify whether the new claim is true. The original note is confusing, but I'm not sure the suggestions improves it much.

[codewithdaniel1]

Thanks for the review. I looked into the Docker CLI documentation and updated the note to make the distinction more specific and verifiable.

The updated note now explains that:

• --gpus is used with docker run / docker container run
• Swarm nodes advertise NVIDIA GPUs as generic resources
• Swarm services request those resources with --generic-resource

The supporting Docker documentation is here:

• https://docs.docker.com/reference/cli/docker/container/run/#access-an-nvidia-gpu
• https://docs.docker.com/reference/cli/dockerd/#node-generic-resources
• https://docs.docker.com/reference/cli/docker/service/create/#generic-resources

I changed the note to:

The --gpus flag provides GPU access to containers created with
docker run. To make GPUs available to services in a swarm, advertise them
as node generic resources and request them with --generic-resource.

I avoided making a claim about what the original wording historically meant and instead described the currently documented behavior directly. Will this version work?