[GH-ISSUE #386] Docker Run command for nvidia(container toolkit) seems to contain stuff related to AMD CDI? #258

New issue

Closed

opened 2026-10-15 12:58:53 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 12:58:53 +00:00

Owner

Originally created by @Fjox on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/386

root@EZVDI:~# docker run \
>     --name wolf \
>     --network=host \
>     -v /etc/wolf:/etc/wolf:rw \
>     -v /var/run/docker.sock:/var/run/docker.sock:rw \
>     -e NVIDIA_DRIVER_CAPABILITIES=all \
>     -e NVIDIA_VISIBLE_DEVICES=all \
>     --gpus=all \
>     --device /dev/dri/ \
>     --device /dev/uinput \
>     --device /dev/uhid \
>     -v /dev/:/dev/:rw \
>     -v /run/udev:/run/udev:rw \
>     --device-cgroup-rule "c 13:* rmw" \
>     ghcr.io/games-on-whales/wolf:stable
docker: Error response from daemon: AMD CDI spec not found

Run 'docker run --help' for more information

OS: Debian 13
GPU: zotac 1080ti
NVidia driver: 550.163.01(installed with apt)
NVidia container toolkit: 1.19.0

Originally created by @Fjox on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/386 ``` root@EZVDI:~# docker run \ > --name wolf \ > --network=host \ > -v /etc/wolf:/etc/wolf:rw \ > -v /var/run/docker.sock:/var/run/docker.sock:rw \ > -e NVIDIA_DRIVER_CAPABILITIES=all \ > -e NVIDIA_VISIBLE_DEVICES=all \ > --gpus=all \ > --device /dev/dri/ \ > --device /dev/uinput \ > --device /dev/uhid \ > -v /dev/:/dev/:rw \ > -v /run/udev:/run/udev:rw \ > --device-cgroup-rule "c 13:* rmw" \ > ghcr.io/games-on-whales/wolf:stable docker: Error response from daemon: AMD CDI spec not found Run 'docker run --help' for more information ``` OS: Debian 13 GPU: zotac 1080ti NVidia driver: 550.163.01(installed with apt) NVidia container toolkit: 1.19.0

bsakaguchi closed this issue

2026-10-15 12:58:54 +00:00

bsakaguchi commented

2026-10-15 12:58:55 +00:00

Author

Owner

@Fjox commented on GitHub (Apr 9, 2026):

for some reason modeset=0 makes docker yap about AMD stuff. totally not confusing

@Fjox commented on GitHub (Apr 9, 2026): for some reason modeset=0 makes docker yap about AMD stuff. totally not confusing