games-on-whales/wolf
1
0
Fork 0
mirror of https://github.com/games-on-whales/wolf.git synced 2026-10-15 21:12:08 +00:00
Code Issues 119 Projects Packages Wiki Activity

[GH-ISSUE #394] Wolf ui no longer connecting to wayland/X11 #261

New issue
Closed
opened 2026-10-15 12:58:56 +00:00 by bsakaguchi · 10 comments
bsakaguchi commented 2026-10-15 12:58:56 +00:00
Owner
Copy link

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

I set up the container using the quickstart and have been using it happily until today the wolf UI no longer loads. I have moved my wolf volume to a new disk, but no other changes. Was I meant to change something in the config files with the new path.

The test app still works and nvidia-smi shows wolf as an active process.

services:
  wolf:
    deploy:
      resources:
        reservations:
          devices:
            - capabilities:
                - gpu
              count: all
              driver: nvidia
    device_cgroup_rules:
      - c 13:* rmw
    devices:
      - /dev/dri
      - /dev/uinput
      - /dev/uhid
    environment:
      - NVIDIA_DRIVER_CAPABILITIES=all
      - NVIDIA_VISIBLE_DEVICES=all
      - WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000
      - WOLF_STOP_CONTAINER_ON_EXIT=false
    image: ghcr.io/games-on-whales/wolf:stable
    network_mode: host
    restart: unless-stopped
    volumes:
      - /new/disk/wolf/data:/etc/wolf
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
version: '3'

Container logs for wolf-ui

[2026-04-19 04:36:43] 
[2026-04-19 04:36:43] [ /etc/cont-init.d/10-setup_user.sh: executing... ]
[2026-04-19 04:36:43] **** Configure default user ****
[2026-04-19 04:36:43] Container running as root. Nothing to do.
[2026-04-19 04:36:43] DONE
[2026-04-19 04:36:43] 
[2026-04-19 04:36:43] [ /etc/cont-init.d/15-setup_devices.sh: executing... ]
[2026-04-19 04:36:43] **** Configure devices ****
[2026-04-19 04:36:43] Exec device groups
[2026-04-19 04:36:43] Path '/dev/input/event*' is not present.
[2026-04-19 04:36:43] Adding user 'root' to groups: root
[2026-04-19 04:36:43] DONE
[2026-04-19 04:36:43] 
[2026-04-19 04:36:43] [ /etc/cont-init.d/30-nvidia.sh: executing... ]
[2026-04-19 04:36:43] Nvidia driver detected, assuming it's using the nvidia driver volume
[2026-04-19 04:36:43] Creating json nvidia_icd.json file
[2026-04-19 04:36:43] 
[2026-04-19 04:36:43] [ /etc/cont-init.d/init-gamescope.sh: executing... ]
[2026-04-19 04:36:43] Launching the container's startup script as user 'root'
[2026-04-19 04:36:43] Starting Wolf-UI
[2026-04-19 04:36:43] [exec] Starting: wolf-ui -f -t
ERROR: Can't connect to a Wayland display.
   at: init (platform/linuxbsd/wayland/wayland_thread.cpp:3909)
ERROR: Could not initialize the Wayland thread.
   at: DisplayServerWayland (platform/linuxbsd/wayland/display_server_wayland.cpp:1417)
ERROR: Can't create the Wayland display server.
   at: create_func (platform/linuxbsd/wayland/display_server_wayland.cpp:1391)
WARNING: Display driver wayland failed, falling back to x11.
     at: setup2 (main/main.cpp:3045)
ERROR: X11 Display is not available
   at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:6586)
ERROR: Unable to create DisplayServer, all display drivers failed.
Use "--headless" command line argument to run the engine in headless mode if this is desired (e.g. for continuous integration).
   at: setup2 (main/main.cpp:3055)

The wolf UI config is the same as the quick start.

Originally created by @eco9898 on GitHub (Apr 19, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/394 I set up the container using the [quickstart](https://games-on-whales.github.io/wolf/stable/user/quickstart.html) and have been using it happily until today the wolf UI no longer loads. I have moved my wolf volume to a new disk, but no other changes. Was I meant to change something in the config files with the new path. The test app still works and nvidia-smi shows wolf as an active process. ```yaml services: wolf: deploy: resources: reservations: devices: - capabilities: - gpu count: all driver: nvidia device_cgroup_rules: - c 13:* rmw devices: - /dev/dri - /dev/uinput - /dev/uhid environment: - NVIDIA_DRIVER_CAPABILITIES=all - NVIDIA_VISIBLE_DEVICES=all - WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000 - WOLF_STOP_CONTAINER_ON_EXIT=false image: ghcr.io/games-on-whales/wolf:stable network_mode: host restart: unless-stopped volumes: - /new/disk/wolf/data:/etc/wolf - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/:/dev/:rw - /run/udev:/run/udev:rw version: '3' ``` Container logs for wolf-ui ``` [2026-04-19 04:36:43] [2026-04-19 04:36:43] [ /etc/cont-init.d/10-setup_user.sh: executing... ] [2026-04-19 04:36:43] **** Configure default user **** [2026-04-19 04:36:43] Container running as root. Nothing to do. [2026-04-19 04:36:43] DONE [2026-04-19 04:36:43] [2026-04-19 04:36:43] [ /etc/cont-init.d/15-setup_devices.sh: executing... ] [2026-04-19 04:36:43] **** Configure devices **** [2026-04-19 04:36:43] Exec device groups [2026-04-19 04:36:43] Path '/dev/input/event*' is not present. [2026-04-19 04:36:43] Adding user 'root' to groups: root [2026-04-19 04:36:43] DONE [2026-04-19 04:36:43] [2026-04-19 04:36:43] [ /etc/cont-init.d/30-nvidia.sh: executing... ] [2026-04-19 04:36:43] Nvidia driver detected, assuming it's using the nvidia driver volume [2026-04-19 04:36:43] Creating json nvidia_icd.json file [2026-04-19 04:36:43] [2026-04-19 04:36:43] [ /etc/cont-init.d/init-gamescope.sh: executing... ] [2026-04-19 04:36:43] Launching the container's startup script as user 'root' [2026-04-19 04:36:43] Starting Wolf-UI [2026-04-19 04:36:43] [exec] Starting: wolf-ui -f -t ERROR: Can't connect to a Wayland display. at: init (platform/linuxbsd/wayland/wayland_thread.cpp:3909) ERROR: Could not initialize the Wayland thread. at: DisplayServerWayland (platform/linuxbsd/wayland/display_server_wayland.cpp:1417) ERROR: Can't create the Wayland display server. at: create_func (platform/linuxbsd/wayland/display_server_wayland.cpp:1391) WARNING: Display driver wayland failed, falling back to x11. at: setup2 (main/main.cpp:3045) ERROR: X11 Display is not available at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:6586) ERROR: Unable to create DisplayServer, all display drivers failed. Use "--headless" command line argument to run the engine in headless mode if this is desired (e.g. for continuous integration). at: setup2 (main/main.cpp:3055) ``` The wolf UI config is the same as the quick start.
bsakaguchi commented 2026-10-15 12:58:57 +00:00
Author
Owner
Copy link

@JBailes commented on GitHub (Apr 19, 2026):

@eco9898 Pull the latest images. This is likely a bug from the recent XWayland modifications in older images.

<!-- gh-comment-id:4275452852 --> @JBailes commented on GitHub (Apr 19, 2026): @eco9898 Pull the latest images. This is likely a bug from the recent XWayland modifications in older images.
bsakaguchi commented 2026-10-15 12:58:57 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Apr 21, 2026):

@JBailes I cleared the cached images and it did not help. The images used for wolf are recent. But the wolf-ui image is about 5 months old. Did you mean to move it to the alpha branch?

<!-- gh-comment-id:4287242433 --> @eco9898 commented on GitHub (Apr 21, 2026): @JBailes I cleared the cached images and it did not help. The images used for wolf are recent. But the wolf-ui image is about 5 months old. Did you mean to move it to the alpha branch?
bsakaguchi commented 2026-10-15 12:58:57 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Apr 21, 2026):

When using alpha for wolf and wolf-ui the same error occurs.

<!-- gh-comment-id:4287305292 --> @eco9898 commented on GitHub (Apr 21, 2026): When using alpha for wolf and wolf-ui the same error occurs.
bsakaguchi commented 2026-10-15 12:58:57 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Apr 21, 2026):

Next thing I can try is using an older wolf image if it is due to a recent change

<!-- gh-comment-id:4287308996 --> @eco9898 commented on GitHub (Apr 21, 2026): Next thing I can try is using an older wolf image if it is due to a recent change
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@JBailes commented on GitHub (Apr 22, 2026):

I duplicated this locally finally. Have a fix.

<!-- gh-comment-id:4299715156 --> @JBailes commented on GitHub (Apr 22, 2026): I duplicated this locally finally. Have a fix.
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@JBailes commented on GitHub (Apr 23, 2026):

Fix in https://github.com/games-on-whales/wolf/pull/397

<!-- gh-comment-id:4304405193 --> @JBailes commented on GitHub (Apr 23, 2026): Fix in https://github.com/games-on-whales/wolf/pull/397
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Jun 19, 2026):

@JBailes I deleted the image cache and pulled the latest images and it looks like the DMA changes have raised a stack trace in the main wolf container.

_ix-wolf-wolf-1_logs (1).txt
_Wolf-UI_9773201241745155866_logs.txt

<!-- gh-comment-id:4748507477 --> @eco9898 commented on GitHub (Jun 19, 2026): @JBailes I deleted the image cache and pulled the latest images and it looks like the DMA changes have raised a stack trace in the main wolf container. [_ix-wolf-wolf-1_logs (1).txt](https://github.com/user-attachments/files/29120391/_ix-wolf-wolf-1_logs.1.txt) [_Wolf-UI_9773201241745155866_logs.txt](https://github.com/user-attachments/files/29120390/_Wolf-UI_9773201241745155866_logs.txt)
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@ABeltramo commented on GitHub (Jun 19, 2026):

One thing that stands out from the logs is

WARN  | Nvidia DRM is not loaded with the flag modeset=1

Can you make sure that nvidia-drm.modeset=1 is in your Linux kernel module options? See the ArchWiki for more info

<!-- gh-comment-id:4750500801 --> @ABeltramo commented on GitHub (Jun 19, 2026): One thing that stands out from the logs is ``` WARN | Nvidia DRM is not loaded with the flag modeset=1 ``` Can you make sure that `nvidia-drm.modeset=1` is in your Linux kernel module options? See [the ArchWiki](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) for more info
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Jun 20, 2026):

nvidia-drm.modeset=1 worked. Not sure if this was disabled at somepoint as wolf was previously working on the late 2025 images, or if this was a new requirement with the new images that included the related fix above. Just started a permission/user overhaul on my server so my game config isn't loading, but everything else looks to be working now. Just gotta fix up the new user permissions on the disk. 😄

<!-- gh-comment-id:4757171847 --> @eco9898 commented on GitHub (Jun 20, 2026): nvidia-drm.modeset=1 worked. Not sure if this was disabled at somepoint as wolf was previously working on the late 2025 images, or if this was a new requirement with the new images that included the related fix above. Just started a permission/user overhaul on my server so my game config isn't loading, but everything else looks to be working now. Just gotta fix up the new user permissions on the disk. 😄
bsakaguchi commented 2026-10-15 12:58:58 +00:00
Author
Owner
Copy link

@eco9898 commented on GitHub (Jun 20, 2026):

Looks good now, thanks both of you for your help.

<!-- gh-comment-id:4757189661 --> @eco9898 commented on GitHub (Jun 20, 2026): Looks good now, thanks both of you for your help.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
beta
feat/fedora-base-images
stable
axolotlitehotfix/randomly-generated-client-id
feat/vulkan-image
ci/image-smoke-harness
nv12-producer-pin
fix/nvidia-zero-copy
fix/amd-dma-buf-negotiation
fix/joypad-input-leak
codex/party-mode-split-render
ci-fedora-images
test/gst-wld-block-linear
fix/nvidia-blackwell-zero-copy
feat/embed-wolf-den
fix/fake-udev-write-db
fix/session-runner-user
fedora-dockerfile
feat/comprehensive-display-modes
aimee/quickstart-scripts
JBailes-patch-1
dev-nix
dev-fake-uinput
dev-tracy
fix/gst_vaapi
v2024.07
v2023.06
v2023.02
v2022.11
Labels
Clear labels   
🧠 1 - 🤖 999

   
AMD

   
bug

   
bug

   
cannot reproduce

   
documentation

   
duplicate

   
easy

   
enhancement

   
enhancement

   
enhancement

   
fixed?

   
fixed?

   
good first issue

   
hard

   
help wanted

   
Intel

   
invalid

   
LXC

   
medium

   
moonlight-protocol

   
Multi GPU

   
nixos

   
not a bug

   
nvidia

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#261
No description provided.