[GH-ISSUE #240] Container Stream will not start with custom render node #165

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

Originally created by @MNarath1 on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/240

When changing the Render node from 128 to 129 trough an enviromental variable containers like steam will be unable to start up properly leading to a failed stream

Log of Steam Container:

[2025-08-12 20:28:59] 
[2025-08-12 20:28:59] [ /etc/cont-init.d/10-setup_user.sh: executing... ]
[2025-08-12 20:28:59] **** Configure default user ****
[2025-08-12 20:28:59] Setting default user uid=1000(retro) gid=1000(retro)
userdel: ubuntu mail spool (/var/mail/ubuntu) not found
useradd: warning: the home directory /home/retro already exists.
useradd: Not copying any file from skel directory into it.
[2025-08-12 20:28:59] Setting umask to 000
[2025-08-12 20:28:59] Ensure retro home directory is writable
[2025-08-12 20:28:59] Ensure XDG_RUNTIME_DIR is writable
[2025-08-12 20:28:59] DONE
[2025-08-12 20:28:59] 
[2025-08-12 20:28:59] [ /etc/cont-init.d/15-setup_devices.sh: executing... ]
[2025-08-12 20:28:59] **** Configure devices ****
[2025-08-12 20:28:59] Exec device groups
[2025-08-12 20:28:59] Path '/dev/input/*' is not present.
[2025-08-12 20:28:59] Path '/dev/nvidia*' is not present.
[2025-08-12 20:28:59] Adding user 'retro' to groups: gow-gid-105,irc
[2025-08-12 20:28:59] DONE
[2025-08-12 20:28:59] 
[2025-08-12 20:28:59] [ /etc/cont-init.d/30-nvidia.sh: executing... ]
[2025-08-12 20:28:59] 
[2025-08-12 20:28:59] [ /etc/cont-init.d/init-gamescope.sh: executing... ]
[2025-08-12 20:28:59] 
[2025-08-12 20:28:59] [ /etc/cont-init.d/system-services.sh: executing... ]
*** DBus started ***
*** Bluez started ***
bluetoothd[73]: Bluetooth daemon 5.79
bluetoothd[73]: src/adapter.c:adapter_init() Failed to access management interface
bluetoothd[73]: src/main.c:main() Adapter handling initialization failed
*** NetworkManager started ***
[2025-08-12 20:28:59] Launching the container's startup script as user 'retro'
[2025-08-12 20:28:59] Steam startup.sh
[2025-08-12 20:28:59] [Sway] - Starting: `/usr/games/steam -bigpicture`
amdgpu: amdgpu_cs_ctx_create2 failed. (-13) 

in this case 128 was a intel intigrated gpu and 129 was an amd RX7900 XTX.
When the intigrated gpu is disabled the RX7900 XTX will work just fine trough.

Originally created by @MNarath1 on GitHub (Aug 12, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/240 When changing the Render node from 128 to 129 trough an enviromental variable containers like steam will be unable to start up properly leading to a failed stream Log of Steam Container: ``` [2025-08-12 20:28:59] [2025-08-12 20:28:59] [ /etc/cont-init.d/10-setup_user.sh: executing... ] [2025-08-12 20:28:59] **** Configure default user **** [2025-08-12 20:28:59] Setting default user uid=1000(retro) gid=1000(retro) userdel: ubuntu mail spool (/var/mail/ubuntu) not found useradd: warning: the home directory /home/retro already exists. useradd: Not copying any file from skel directory into it. [2025-08-12 20:28:59] Setting umask to 000 [2025-08-12 20:28:59] Ensure retro home directory is writable [2025-08-12 20:28:59] Ensure XDG_RUNTIME_DIR is writable [2025-08-12 20:28:59] DONE [2025-08-12 20:28:59] [2025-08-12 20:28:59] [ /etc/cont-init.d/15-setup_devices.sh: executing... ] [2025-08-12 20:28:59] **** Configure devices **** [2025-08-12 20:28:59] Exec device groups [2025-08-12 20:28:59] Path '/dev/input/*' is not present. [2025-08-12 20:28:59] Path '/dev/nvidia*' is not present. [2025-08-12 20:28:59] Adding user 'retro' to groups: gow-gid-105,irc [2025-08-12 20:28:59] DONE [2025-08-12 20:28:59] [2025-08-12 20:28:59] [ /etc/cont-init.d/30-nvidia.sh: executing... ] [2025-08-12 20:28:59] [2025-08-12 20:28:59] [ /etc/cont-init.d/init-gamescope.sh: executing... ] [2025-08-12 20:28:59] [2025-08-12 20:28:59] [ /etc/cont-init.d/system-services.sh: executing... ] *** DBus started *** *** Bluez started *** bluetoothd[73]: Bluetooth daemon 5.79 bluetoothd[73]: src/adapter.c:adapter_init() Failed to access management interface bluetoothd[73]: src/main.c:main() Adapter handling initialization failed *** NetworkManager started *** [2025-08-12 20:28:59] Launching the container's startup script as user 'retro' [2025-08-12 20:28:59] Steam startup.sh [2025-08-12 20:28:59] [Sway] - Starting: `/usr/games/steam -bigpicture` amdgpu: amdgpu_cs_ctx_create2 failed. (-13) ``` in this case 128 was a intel intigrated gpu and 129 was an amd RX7900 XTX. When the intigrated gpu is disabled the RX7900 XTX will work just fine trough.
Author
Owner

@ABeltramo commented on GitHub (Aug 12, 2025):

Please post the full Wolf logs with the env variable WOLF_LOG_LEVEL=DEBUG and the exact docker run command that you are using to run it with the dual GPU setup.

Are you setting the encoder node and the render node to the same GPU?

<!-- gh-comment-id:3180576317 --> @ABeltramo commented on GitHub (Aug 12, 2025): Please post the full Wolf logs with the env variable `WOLF_LOG_LEVEL=DEBUG` and the exact docker run command that you are using to run it with the dual GPU setup. Are you setting the encoder node and the render node to the same GPU?
Author
Owner

@ABeltramo commented on GitHub (Nov 27, 2025):

There's been a lot of work on this lately. For a dual Intel/AMD GPU setup you'll still have to manually exclude the render device from the mount points, but something like

  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - WOLF_RENDER_NODE=/dev/dri/renderD129
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/input:/dev/input:rw
      - /run/udev:/run/udev:rw
      - /etc/wolf:/etc/wolf:rw 
    device_cgroup_rules:
      - 'c 13:* rmw'
    devices:
      - /dev/dri/renderD129 # Instead of mounting the full `/dev/dri` we only show Wolf the second GPU
      - /dev/uinput
      - /dev/uhid
    restart: unless-stopped
    network_mode: host

has been reported https://github.com/games-on-whales/wolf/issues/297#issuecomment-3567587676 working

<!-- gh-comment-id:3585039269 --> @ABeltramo commented on GitHub (Nov 27, 2025): There's been a lot of work on this lately. For a dual Intel/AMD GPU setup you'll still have to manually exclude the render device from the mount points, but something like ```yaml wolf: image: ghcr.io/games-on-whales/wolf:stable environment: - WOLF_RENDER_NODE=/dev/dri/renderD129 volumes: - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/input:/dev/input:rw - /run/udev:/run/udev:rw - /etc/wolf:/etc/wolf:rw device_cgroup_rules: - 'c 13:* rmw' devices: - /dev/dri/renderD129 # Instead of mounting the full `/dev/dri` we only show Wolf the second GPU - /dev/uinput - /dev/uhid restart: unless-stopped network_mode: host ``` has been reported https://github.com/games-on-whales/wolf/issues/297#issuecomment-3567587676 working
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#165
No description provided.