[GH-ISSUE #263] (AMD) Wrong configuration results in error #181

Closed
opened 2026-10-15 12:57:46 +00:00 by bsakaguchi · 3 comments
Owner

Originally created by @KorinFlakes on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/263

Wolf fails to bind the GPU compositor (weirdly enough, wolf was working flawlessly before I rebooted my PC)

System:
Nobara Linux 42 (KDE Plasma Desktop Edition) x86_64
Kernel: 6.16.9-200.nobara.fc42.x86_64
CPU: AMD Ryzen 5 5600 (12) @ 4.47 GHz
GPU: AMD Radeon RX 6700 XT
Mesa: radeonsi, RADV NAVI22

Inside container:
glxinfo and vulkaninfo detect GPU correctly
/dev/dri/card1 and renderD128 present

Presently resorted to running wolf through a docker-compose:

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    container_name: wolf
    network_mode: host
    privileged: true
    environment:
      - DISPLAY=:0
      - WOLF_DRM_DEVICE=/dev/dri/card1
    volumes:
      - /tmp/.X11-unix:/tmp/.X11-unix
      - /dev:/dev
      - /run/udev:/run/udev
      - /var/lib/dbus:/var/lib/dbus
    devices:
      - /dev/dri:/dev/dri
    restart: unless-stopped

I was previously running it through a script:

launch-wolf.sh

TBH I can barely remember what's in it, I've changed it so many bloody times trying to get it to work now.

The logs

If you need any other information please don't hesitate to ask, I'm just very tired right now.

Originally created by @KorinFlakes on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/263 Wolf fails to bind the GPU compositor (weirdly enough, wolf was working flawlessly before I rebooted my PC) > System: > Nobara Linux 42 (KDE Plasma Desktop Edition) x86_64 > Kernel: 6.16.9-200.nobara.fc42.x86_64 > CPU: AMD Ryzen 5 5600 (12) @ 4.47 GHz > GPU: AMD Radeon RX 6700 XT > Mesa: radeonsi, RADV NAVI22 Inside container: glxinfo and vulkaninfo detect GPU correctly /dev/dri/card1 and renderD128 present Presently resorted to running wolf through a docker-compose: ```yaml services: wolf: image: ghcr.io/games-on-whales/wolf:stable container_name: wolf network_mode: host privileged: true environment: - DISPLAY=:0 - WOLF_DRM_DEVICE=/dev/dri/card1 volumes: - /tmp/.X11-unix:/tmp/.X11-unix - /dev:/dev - /run/udev:/run/udev - /var/lib/dbus:/var/lib/dbus devices: - /dev/dri:/dev/dri restart: unless-stopped ``` I was previously running it through a script: [launch-wolf.sh](https://gist.github.com/KorinFlakes/150458f7c32112b9e0b806faa833e847) TBH I can barely remember what's in it, I've changed it so many bloody times trying to get it to work now. [The logs](https://gist.github.com/KorinFlakes/e37081b2c99da00854b634f364ffb773.js) If you need any other information please don't hesitate to ask, I'm just very tired right now.
Author
Owner

@Marshy-Madness commented on GitHub (Oct 8, 2025):

When I had this similar issue I had to do rebuilt the nvidia image.

I had to remove the old image first. I can't find the command I ran anywhere

curl https://raw.githubusercontent.com/games-on-whales/gow/master/images/nvidia-driver/Dockerfile | docker build -t gow/nvidia-driver:latest -f - --build-arg NV_VERSION=$(cat /sys/module/nvidia/version) .

docker create --rm --mount source=nvidia-driver-vol,destination=/usr/nvidia gow/nvidia-driver:latest sh

<!-- gh-comment-id:3382483249 --> @Marshy-Madness commented on GitHub (Oct 8, 2025): When I had this similar issue I had to do rebuilt the nvidia image. I had to remove the old image first. I can't find the command I ran anywhere ` curl https://raw.githubusercontent.com/games-on-whales/gow/master/images/nvidia-driver/Dockerfile | docker build -t gow/nvidia-driver:latest -f - --build-arg NV_VERSION=$(cat /sys/module/nvidia/version) .` `docker create --rm --mount source=nvidia-driver-vol,destination=/usr/nvidia gow/nvidia-driver:latest sh`
Author
Owner

@ABeltramo commented on GitHub (Oct 8, 2025):

@KorinFlakes your compose configuration is all wrong, can you try with the standard one in the quickstart guide first

version: "3"
services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    volumes:
      - /etc/wolf/:/etc/wolf
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
    device_cgroup_rules:
      - 'c 13:* rmw'
    devices:
      - /dev/dri
      - /dev/uinput
      - /dev/uhid
    network_mode: host
    restart: unless-stopped

and then, if you still have issues, post the full Wolf logs using the command

docker logs wolf

the ones that you've posted are impossible to read (and looks incomplete too) unfortunately

<!-- gh-comment-id:3382755259 --> @ABeltramo commented on GitHub (Oct 8, 2025): @KorinFlakes your compose configuration is all wrong, can you try with the standard one in the [quickstart guide](https://games-on-whales.github.io/wolf/stable/user/quickstart.html) first ```yaml version: "3" services: wolf: image: ghcr.io/games-on-whales/wolf:stable volumes: - /etc/wolf/:/etc/wolf - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/:/dev/:rw - /run/udev:/run/udev:rw device_cgroup_rules: - 'c 13:* rmw' devices: - /dev/dri - /dev/uinput - /dev/uhid network_mode: host restart: unless-stopped ``` and then, if you still have issues, post the full Wolf logs using the command ``` docker logs wolf ``` the ones that you've posted are impossible to read (and looks incomplete too) unfortunately
Author
Owner

@ConsularParadi commented on GitHub (Oct 15, 2025):

Hi, I am facing the same issue on a dual GPU laptop. I am running wolf using the Nvidia manual method.

Specifically it identifies the Nvidia GPU in DEBUG logs but I still get this error ERROR | [GSTREAMER] Pipeline error: Internal data stream error.

Here are the logs from wolf container
https://pastebin.com/MJxfLn02

And here is my docker compose

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    container_name: wolf
    environment:
      - NVIDIA_DRIVER_VOLUME_NAME=nvidia-driver-vol
      - WOLF_SOCKET_PATH=/var/run/wolf/wolf.sock
      - WOLF_RENDER_NODE=/dev/dri/renderD129
      - WOLF_LOG_LEVEL=DEBUG
    volumes:
      - ${CONFIG_DIR}/wolf:/etc/wolf:rw
      - /var/run/wolf:/var/run/wolf
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
      - nvidia-driver-vol:/usr/nvidia:rw
    devices:
      - /dev/dri
      - /dev/uinput
      - /dev/uhid
      - /dev/nvidia-uvm
      - /dev/nvidia-uvm-tools
      - /dev/nvidia-caps/nvidia-cap1
      - /dev/nvidia-caps/nvidia-cap2
      - /dev/nvidiactl
      - /dev/nvidia0
      - /dev/nvidia-modeset
    device_cgroup_rules:
      - 'c 13:* rmw'
    network_mode: host
    restart: unless-stopped
  wolfmanager:
    image: ghcr.io/games-on-whales/wolfmanager/wolfmanager:latest
    container_name: wolf-manager
    ports:
      - "3000:3000"
    environment:
      - NODE_ENV=production
      - NEXTAUTH_URL=http://localhost:3000
    volumes:
      - /var/run/wolf:/var/run/wolf # Mount Wolf socket
      - /var/run/docker.sock:/var/run/docker.sock # Mount Docker socket
      - ${CONFIG_DIR}/wolf/wolfmanager:/app/config
    restart: unless-stopped
volumes:
  nvidia-driver-vol:
    external: true

I am on Arch and the Nvidia-smi also shows that the container is using GPU

Wed Oct 15 11:21:55 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.82.09              Driver Version: 580.82.09      CUDA Version: 13.0     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 950M        Off |   00000000:01:00.0 Off |                  N/A |
| N/A   42C    P8            N/A  /  200W |      98MiB /   4096MiB |     11%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A             746      G   niri                                      1MiB |
|    0   N/A  N/A          341247      G   /wolf/wolf                                2MiB |
|    0   N/A  N/A          343371      G   sway                                     21MiB |
|    0   N/A  N/A          343386      G   /usr/lib/firefox/firefox                 39MiB |
+-----------------------------------------------------------------------------------------+
<!-- gh-comment-id:3404629315 --> @ConsularParadi commented on GitHub (Oct 15, 2025): Hi, I am facing the same issue on a dual GPU laptop. I am running wolf using the Nvidia manual method. Specifically it identifies the Nvidia GPU in DEBUG logs but I still get this error ```ERROR | [GSTREAMER] Pipeline error: Internal data stream error.``` Here are the logs from wolf container https://pastebin.com/MJxfLn02 And here is my docker compose ``` services: wolf: image: ghcr.io/games-on-whales/wolf:stable container_name: wolf environment: - NVIDIA_DRIVER_VOLUME_NAME=nvidia-driver-vol - WOLF_SOCKET_PATH=/var/run/wolf/wolf.sock - WOLF_RENDER_NODE=/dev/dri/renderD129 - WOLF_LOG_LEVEL=DEBUG volumes: - ${CONFIG_DIR}/wolf:/etc/wolf:rw - /var/run/wolf:/var/run/wolf - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/:/dev/:rw - /run/udev:/run/udev:rw - nvidia-driver-vol:/usr/nvidia:rw devices: - /dev/dri - /dev/uinput - /dev/uhid - /dev/nvidia-uvm - /dev/nvidia-uvm-tools - /dev/nvidia-caps/nvidia-cap1 - /dev/nvidia-caps/nvidia-cap2 - /dev/nvidiactl - /dev/nvidia0 - /dev/nvidia-modeset device_cgroup_rules: - 'c 13:* rmw' network_mode: host restart: unless-stopped wolfmanager: image: ghcr.io/games-on-whales/wolfmanager/wolfmanager:latest container_name: wolf-manager ports: - "3000:3000" environment: - NODE_ENV=production - NEXTAUTH_URL=http://localhost:3000 volumes: - /var/run/wolf:/var/run/wolf # Mount Wolf socket - /var/run/docker.sock:/var/run/docker.sock # Mount Docker socket - ${CONFIG_DIR}/wolf/wolfmanager:/app/config restart: unless-stopped volumes: nvidia-driver-vol: external: true ``` I am on Arch and the Nvidia-smi also shows that the container is using GPU ``` Wed Oct 15 11:21:55 2025 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 580.82.09 Driver Version: 580.82.09 CUDA Version: 13.0 | +-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce GTX 950M Off | 00000000:01:00.0 Off | N/A | | N/A 42C P8 N/A / 200W | 98MiB / 4096MiB | 11% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | 0 N/A N/A 746 G niri 1MiB | | 0 N/A N/A 341247 G /wolf/wolf 2MiB | | 0 N/A N/A 343371 G sway 21MiB | | 0 N/A N/A 343386 G /usr/lib/firefox/firefox 39MiB | +-----------------------------------------------------------------------------------------+ ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
games-on-whales/wolf#181
No description provided.