[GH-ISSUE #284] Wolf stuck in a restart loop #200

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

Originally created by @Azathoth-88 on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/284

Dear GoW team,

I just noticed this in the past two days that the container stuck in restart loop.
Not sure what it's related to, i'm on Debian 12 with mesa backports.
I tried deleting my config file, with no avail.
Do you have any advice / idea what direction to poke to resolve this?
Thank you in advance!

Here's the container log:

[2025-10-31 12:58:57] 
[2025-10-31 12:58:57] [ /etc/cont-init.d/10-setup_user.sh: executing... ]
[2025-10-31 12:58:57] **** Configure default user ****
[2025-10-31 12:58:57] Container running as root. Nothing to do.
[2025-10-31 12:58:57] DONE
[2025-10-31 12:58:57] 
[2025-10-31 12:58:57] [ /etc/cont-init.d/15-setup_devices.sh: executing... ]
[2025-10-31 12:58:57] **** Configure devices ****
[2025-10-31 12:58:57] Exec device groups
[2025-10-31 12:58:57] Adding user 'root' to groups: gow-gid-102,root
[2025-10-31 12:58:57] DONE
[2025-10-31 12:58:57] 
[2025-10-31 12:58:57] [ /etc/cont-init.d/30-nvidia.sh: executing... ]
[2025-10-31 12:58:57] 
[2025-10-31 12:58:57] [ /etc/cont-init.d/init-gamescope.sh: executing... ]
[2025-10-31 12:58:57] Launching the container's startup script as user 'root'
12:58:57.541736273 INFO  | Gstreamer version: 1.26.2-0
12:58:57.542411214 DEBUG | XDG_RUNTIME_DIR=/tmp/sockets
12:58:57.542433624 INFO  | Reading config file from: /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/config.toml
12:58:57.550391412 DEBUG | /dev/dri/renderD128 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
12:58:57.550422332 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1)
12:58:57.550437082 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1)
**Stack trace (most recent call first):
#0  0x0000558cc1401bd2 in safe_dump_stacktrace_to at /wolf/src/moonlight-server/./exceptions/exceptions.h:22:56
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
#1  0x0000558cc140caed in shutdown_handler at /wolf/src/moonlight-server/./exceptions/exceptions.h:69:28
#2  0x0000558cc1416350 in on_terminate at /wolf/src/moonlight-server/./exceptions/exceptions.h:99:19
#3  0x00007f2c6af290a9 at /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007f2c6af12a9d in std::terminate() at /lib/x86_64-linux-gnu/libstdc++.so.6
#5  (inlined)          in std::__terminate() at /usr/include/x86_64-linux-gnu/c++/14/bits/c++config.h:324:14
#6  0x0000558cc142c40a in std::thread::~thread() at /usr/include/c++/14/bits/std_thread.h:182:18
#7  0x0000558cc13d95d0 in run() at /wolf/src/moonlight-server/wolf.cpp:524:1
#8  0x0000558cc13f7cc4 in main at /wolf/src/moonlight-server/wolf.cpp:537:6
#9  0x00007f2c6ab4d577 at /lib/x86_64-linux-gnu/libc.so.6
#10 0x00007f2c6ab4d63a in __libc_start_main at /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000558cc13fde44 in _start at /wolf/wolf**
0:00:00.046075518     1 0x55addcb7f3a0 WARN                vafilter gstvafilter.c:1787:gst_va_filter_has_compose:<vafilter0> VPP does not support alpha blending
12:58:57.595414359 INFO  | Using H264 encoder: va
12:58:57.595470849 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1)
12:58:57.595487089 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1)
12:58:57.600461834 INFO  | Using HEVC encoder: va
12:58:57.600525274 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1)
12:58:57.600543594 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1)
0:00:00.065211468     1 0x55addcb7f3a0 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "vaav1enc"!
0:00:00.065225578     1 0x55addcb7f3a0 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "vaav1lpenc"!
12:58:57.601090375 INFO  | Using AV1 encoder: aom
12:58:57.601099945 WARN  | Software AV1 encoder detected
12:58:57.601149675 DEBUG | Required DMA formats for vapostproc: ["NV12", "YV12", "YU12", "P010", "P012", "R8  ", "YUYV", "YU24", "AB24", "AR24", "XB24", "XR24", "AR30"]
12:58:57.601180295 INFO  | Using zero copy pipeline on AMD (/dev/dri/renderD128)
12:58:57.601332645 DEBUG | Loading server certificates from disk: /etc/wolf/cfg/cert.pem /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/key.pem
12:58:57.603338227 DEBUG | We are running as container ID 515b225fc3912ae23a9f9862ca0290b0f6790d23d899b90ee00f33bb8477912b
12:58:57.603358697 INFO  | Detected mounted /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf in the host as /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf
12:58:57.603365007 INFO  | Detected mounted /tmp/sockets in the host as /tmp/sockets
12:58:57.603449617 INFO  | [RTP] Starting RTP ping server on ports 48100 and 48200
12:58:57.603505287 INFO  | RTSP server started on port: 48010
12:58:57.603543647 INFO  | HTTP server listening on port: 47989 
12:58:57.603557927 INFO  | Starting API server on /tmp/wolf.sock
12:58:57.603582797 INFO  | Starting mDNS service
12:58:57.603646027 INFO  | Control server started on port: 47999
12:58:57.603868257 DEBUG | [PULSE] Connecting...
12:58:57.603926647 DEBUG | [PULSE] Context failed
12:58:57.603935937 WARN  | [PULSE] Unable to connect, Access denied
12:58:57.603974748 INFO  | Starting PulseAudio docker container
12:58:57.604590488 WARN  | [DOCKER] Container WolfPulseAudio already present, removing first
12:58:57.604793549 INFO  | HTTPS server listening on port: 47984 
wolf exited with code 6 (restarting)

And here's the compose file:

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    container_name: wolf
    logging:
      driver: json-file
    environment:
      - XDG_RUNTIME_DIR=/tmp/sockets
      - HOST_APPS_STATE_FOLDER=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf
      - WOLF_CFG_FILE=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/config.toml
      - WOLF_PRIVATE_KEY_FILE=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/key.pem
      - WOLF_PRIVATE_CERT_FILE/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/cert.pem
      - WOLF_LOG_LEVEL=DEBUG
    volumes:
      - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/:/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf:rw
      - /shelter/media/roms/:/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/client-data/RetroArch/.config/retroarch/roms/ext:rw
      - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg:/etc/wolf/cfg:rw
      - /tmp/sockets:/tmp/sockets:rw
      - /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/card0
      - /dev/dri/renderD128
      - /dev/uinput
      - /dev/uhid
    network_mode: host
    restart: unless-stopped
Originally created by @Azathoth-88 on GitHub (Oct 31, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/284 Dear GoW team, I just noticed this in the past two days that the container stuck in restart loop. Not sure what it's related to, i'm on Debian 12 with mesa backports. I tried deleting my config file, with no avail. Do you have any advice / idea what direction to poke to resolve this? Thank you in advance! Here's the container log: ```shell [2025-10-31 12:58:57] [2025-10-31 12:58:57] [ /etc/cont-init.d/10-setup_user.sh: executing... ] [2025-10-31 12:58:57] **** Configure default user **** [2025-10-31 12:58:57] Container running as root. Nothing to do. [2025-10-31 12:58:57] DONE [2025-10-31 12:58:57] [2025-10-31 12:58:57] [ /etc/cont-init.d/15-setup_devices.sh: executing... ] [2025-10-31 12:58:57] **** Configure devices **** [2025-10-31 12:58:57] Exec device groups [2025-10-31 12:58:57] Adding user 'root' to groups: gow-gid-102,root [2025-10-31 12:58:57] DONE [2025-10-31 12:58:57] [2025-10-31 12:58:57] [ /etc/cont-init.d/30-nvidia.sh: executing... ] [2025-10-31 12:58:57] [2025-10-31 12:58:57] [ /etc/cont-init.d/init-gamescope.sh: executing... ] [2025-10-31 12:58:57] Launching the container's startup script as user 'root' 12:58:57.541736273 INFO | Gstreamer version: 1.26.2-0 12:58:57.542411214 DEBUG | XDG_RUNTIME_DIR=/tmp/sockets 12:58:57.542433624 INFO | Reading config file from: /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/config.toml 12:58:57.550391412 DEBUG | /dev/dri/renderD128 vendor: Advanced Micro Devices, Inc. [AMD/ATI] 12:58:57.550422332 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1) 12:58:57.550437082 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1) **Stack trace (most recent call first): #0 0x0000558cc1401bd2 in safe_dump_stacktrace_to at /wolf/src/moonlight-server/./exceptions/exceptions.h:22:56 amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description. If they do, bad things may happen! #1 0x0000558cc140caed in shutdown_handler at /wolf/src/moonlight-server/./exceptions/exceptions.h:69:28 #2 0x0000558cc1416350 in on_terminate at /wolf/src/moonlight-server/./exceptions/exceptions.h:99:19 #3 0x00007f2c6af290a9 at /lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007f2c6af12a9d in std::terminate() at /lib/x86_64-linux-gnu/libstdc++.so.6 #5 (inlined) in std::__terminate() at /usr/include/x86_64-linux-gnu/c++/14/bits/c++config.h:324:14 #6 0x0000558cc142c40a in std::thread::~thread() at /usr/include/c++/14/bits/std_thread.h:182:18 #7 0x0000558cc13d95d0 in run() at /wolf/src/moonlight-server/wolf.cpp:524:1 #8 0x0000558cc13f7cc4 in main at /wolf/src/moonlight-server/wolf.cpp:537:6 #9 0x00007f2c6ab4d577 at /lib/x86_64-linux-gnu/libc.so.6 #10 0x00007f2c6ab4d63a in __libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 #11 0x0000558cc13fde44 in _start at /wolf/wolf** 0:00:00.046075518 1 0x55addcb7f3a0 WARN vafilter gstvafilter.c:1787:gst_va_filter_has_compose:<vafilter0> VPP does not support alpha blending 12:58:57.595414359 INFO | Using H264 encoder: va 12:58:57.595470849 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1) 12:58:57.595487089 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1) 12:58:57.600461834 INFO | Using HEVC encoder: va 12:58:57.600525274 DEBUG | Skipping NVIDIA encoder, not a NVIDIA GPU (1) 12:58:57.600543594 DEBUG | Skipping QUICKSYNC encoder, not an Intel GPU (1) 0:00:00.065211468 1 0x55addcb7f3a0 WARN GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "vaav1enc"! 0:00:00.065225578 1 0x55addcb7f3a0 WARN GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "vaav1lpenc"! 12:58:57.601090375 INFO | Using AV1 encoder: aom 12:58:57.601099945 WARN | Software AV1 encoder detected 12:58:57.601149675 DEBUG | Required DMA formats for vapostproc: ["NV12", "YV12", "YU12", "P010", "P012", "R8 ", "YUYV", "YU24", "AB24", "AR24", "XB24", "XR24", "AR30"] 12:58:57.601180295 INFO | Using zero copy pipeline on AMD (/dev/dri/renderD128) 12:58:57.601332645 DEBUG | Loading server certificates from disk: /etc/wolf/cfg/cert.pem /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/key.pem 12:58:57.603338227 DEBUG | We are running as container ID 515b225fc3912ae23a9f9862ca0290b0f6790d23d899b90ee00f33bb8477912b 12:58:57.603358697 INFO | Detected mounted /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf in the host as /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf 12:58:57.603365007 INFO | Detected mounted /tmp/sockets in the host as /tmp/sockets 12:58:57.603449617 INFO | [RTP] Starting RTP ping server on ports 48100 and 48200 12:58:57.603505287 INFO | RTSP server started on port: 48010 12:58:57.603543647 INFO | HTTP server listening on port: 47989 12:58:57.603557927 INFO | Starting API server on /tmp/wolf.sock 12:58:57.603582797 INFO | Starting mDNS service 12:58:57.603646027 INFO | Control server started on port: 47999 12:58:57.603868257 DEBUG | [PULSE] Connecting... 12:58:57.603926647 DEBUG | [PULSE] Context failed 12:58:57.603935937 WARN | [PULSE] Unable to connect, Access denied 12:58:57.603974748 INFO | Starting PulseAudio docker container 12:58:57.604590488 WARN | [DOCKER] Container WolfPulseAudio already present, removing first 12:58:57.604793549 INFO | HTTPS server listening on port: 47984 wolf exited with code 6 (restarting) ``` And here's the compose file: ```dockerfile services: wolf: image: ghcr.io/games-on-whales/wolf:stable container_name: wolf logging: driver: json-file environment: - XDG_RUNTIME_DIR=/tmp/sockets - HOST_APPS_STATE_FOLDER=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf - WOLF_CFG_FILE=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/config.toml - WOLF_PRIVATE_KEY_FILE=/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/key.pem - WOLF_PRIVATE_CERT_FILE/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg/cert.pem - WOLF_LOG_LEVEL=DEBUG volumes: - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/:/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf:rw - /shelter/media/roms/:/srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/client-data/RetroArch/.config/retroarch/roms/ext:rw - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/cfg:/etc/wolf/cfg:rw - /tmp/sockets:/tmp/sockets:rw - /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/card0 - /dev/dri/renderD128 - /dev/uinput - /dev/uhid network_mode: host restart: unless-stopped ```
Author
Owner

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

It looks like your docker compose configuration is a mix of legacy and unsupported options that is most likely causing the issue.

Try going back to something closer to what's in the quickstart guide:

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    container_name: wolf
    logging:
      driver: json-file
    environment:
      - WOLF_LOG_LEVEL=DEBUG
    volumes:
      - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/:/etc/wolf:rw
      - /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/card0
      - /dev/dri/renderD128
      - /dev/uinput
      - /dev/uhid
    network_mode: host
    restart: unless-stopped

Newer Wolf versions should take care of fixing up the mount points automatically with this. Make sure to pull latest with:

docker pull ghcr.io/games-on-whales/wolf:stable
<!-- gh-comment-id:3477897441 --> @ABeltramo commented on GitHub (Nov 2, 2025): It looks like your docker compose configuration is a mix of legacy and unsupported options that is most likely causing the issue. Try going back to something closer to what's in the quickstart guide: ```yaml services: wolf: image: ghcr.io/games-on-whales/wolf:stable container_name: wolf logging: driver: json-file environment: - WOLF_LOG_LEVEL=DEBUG volumes: - /srv/dev-disk-by-uuid-95ec51e3-4287-4aa0-bc4d-cbb9ffa9bbd6/wolf/:/etc/wolf:rw - /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/card0 - /dev/dri/renderD128 - /dev/uinput - /dev/uhid network_mode: host restart: unless-stopped ``` Newer Wolf versions should take care of fixing up the mount points automatically with this. Make sure to pull latest with: ``` docker pull ghcr.io/games-on-whales/wolf:stable ```
Author
Owner

@Azathoth-88 commented on GitHub (Nov 4, 2025):

This fixed the issue, thank you!
I also had to purge the image first then re-pull it, otherwise it'd throw the same error.
But admittably i haven't changed this compose file for a long time now (as it "just works") :)
Thank you again for your help!

<!-- gh-comment-id:3485188309 --> @Azathoth-88 commented on GitHub (Nov 4, 2025): This fixed the issue, thank you! I also had to purge the image first then re-pull it, otherwise it'd throw the same error. But admittably i haven't changed this compose file for a long time now (as it "just works") :) Thank you again for your help!
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#200
No description provided.