games-on-whales/wolf

Fork 0

mirror of https://github.com/games-on-whales/wolf.git synced 2026-10-15 21:12:08 +00:00

[GH-ISSUE #295] Apps not being added with new install #206

New issue

Closed

opened 2026-10-15 12:58:12 +00:00 by bsakaguchi · 6 comments

bsakaguchi commented

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

Owner

Originally created by @jakepi84 on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/295

Have a bit of a head scratcher. I am attempting to setup Wolf on a new machine. It is running Debian 13 on bare metal. Below is my compose file. Everything is pretty straightforward, but for some reason none of the default apps are appearing in Moonlight? I see the app configured in the default toml. I am at a bit of a loss on this one. Attaching a screenshot and my logs.

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - TZ=America/Chicago
      - WOLF_RENDER_NODE=/dev/dri/renderD129
      - WOLF_ENCODER_NODE=/dev/dri/renderD128
      - WOLF_LOG_LEVEL=DEBUG
    volumes:
      - /srv/wolf:/etc/wolf
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /tmp/sockets:/tmp/sockets:rw
    device_cgroup_rules:
      - 'c 13:* rmw'
    devices:
      - /dev/dri
      - /dev/uinput
      - /dev/uhid
    network_mode: host
    restart: unless-stopped

log.txt

Originally created by @jakepi84 on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/295 Have a bit of a head scratcher. I am attempting to setup Wolf on a new machine. It is running Debian 13 on bare metal. Below is my compose file. Everything is pretty straightforward, but for some reason none of the default apps are appearing in Moonlight? I see the app configured in the default toml. I am at a bit of a loss on this one. Attaching a screenshot and my logs. ```yaml services: wolf: image: ghcr.io/games-on-whales/wolf:stable environment: - TZ=America/Chicago - WOLF_RENDER_NODE=/dev/dri/renderD129 - WOLF_ENCODER_NODE=/dev/dri/renderD128 - WOLF_LOG_LEVEL=DEBUG volumes: - /srv/wolf:/etc/wolf - /dev/:/dev/:rw - /run/udev:/run/udev:rw - /var/run/docker.sock:/var/run/docker.sock:rw - /tmp/sockets:/tmp/sockets:rw device_cgroup_rules: - 'c 13:* rmw' devices: - /dev/dri - /dev/uinput - /dev/uhid network_mode: host restart: unless-stopped ``` [log.txt](https://github.com/user-attachments/files/23658829/log.txt) <img width="1266" height="585" alt="Image" src="https://github.com/user-attachments/assets/df0075f6-35e2-4649-bd38-422a49b7f71d" />

bsakaguchi closed this issue

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

bsakaguchi commented

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

Author

Owner

@scottsweb commented on GitHub (Nov 20, 2025):

Select "Wolf UI" in this screenshot, does that give you the apps you expect to see?

@scottsweb commented on GitHub (Nov 20, 2025): Select "Wolf UI" in this screenshot, does that give you the apps you expect to see?

bsakaguchi commented

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

Author

Owner

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

You are seeing the new Wolf UI which we've just recently merged before I managed to update the docs 😉 If you open up Wolf UI from Moonlight you'll be able to access all the apps, user profiles, lobbies and more functionality that just wasn't possible in Moonlight itself.

On a separate note, I highly suggest to also remove the split between GPUs

      - WOLF_RENDER_NODE=/dev/dri/renderD129
      - WOLF_ENCODER_NODE=/dev/dri/renderD128

with the new zero copy video pipelines that we've implemented you should pick a card and stick with it. Those options will most likely be removed soon because they aren't needed anymore.

@ABeltramo commented on GitHub (Nov 20, 2025): You are seeing the new Wolf UI which we've just recently merged before I managed to update the docs 😉 If you open up `Wolf UI` from Moonlight you'll be able to access all the apps, user profiles, lobbies and more functionality that just wasn't possible in Moonlight itself. On a separate note, I highly suggest to also remove the split between GPUs ``` - WOLF_RENDER_NODE=/dev/dri/renderD129 - WOLF_ENCODER_NODE=/dev/dri/renderD128 ``` with the new zero copy video pipelines that we've implemented you should pick a card and stick with it. Those options will most likely be removed soon because they aren't needed anymore.

bsakaguchi commented

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

Author

Owner

@jakepi84 commented on GitHub (Nov 20, 2025):

Alright, the problem was between the keyboard and seat! I get it now, if I launch the Wolf UI is see my apps.

@ABeltramo I have it split currently to use my Intel Arc for encode and AMD for render. If I wanted to force Wolf to use just the AMD (renderD129) what is the best way to do this?

Thank you again for all the hard work!

@jakepi84 commented on GitHub (Nov 20, 2025): Alright, the problem was between the keyboard and seat! I get it now, if I launch the Wolf UI is see my apps. @ABeltramo I have it split currently to use my Intel Arc for encode and AMD for render. If I wanted to force Wolf to use just the AMD (renderD129) what is the best way to do this? Thank you again for all the hard work!

bsakaguchi commented

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

Author

Owner

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

I have it split currently to use my Intel Arc for encode and AMD for render. If I wanted to force Wolf to use just the AMD (renderD129) what is the best way to do this?

Ideally you would just set WOLF_RENDER_NODE=/dev/dri/renderD129 and that should be it. Unfortunately, since you have 2 VAAPI capable GPUs (Intel+AMD), there's currently an issue with that were a little part of our Gstreamer pipeline defaults to /dev/dri/renderD128 messing everything up.
Can you try something like the following?

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - WOLF_LOG_LEVEL=DEBUG
      - WOLF_RENDER_NODE=/dev/dri/renderD129
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/input:/dev/input:rw
      - /mnt/udev:/run/udev:rw
      - /srv/wolf:/etc/wolf:rw
    device_cgroup_rules:
      - 'c 13:* rmw'
    devices:
      - /dev/dri/renderD129
      - /dev/uinput
      - /dev/uhid
    restart: unless-stopped
    network_mode: host

The idea is that we only expose one GPU to Wolf (/dev/dri/renderD129) instead of the full /dev/. That will break DualSense joypad support (because it needs access to /dev/hidrawX devices, which is why we mount the full /dev/) but apart from that everything else should work. Let me know if that works for you!

We've just recently fixed multi-GPU selection for Nvidia, the next one up is definitely Intel/AMD but no ETA yet..

@ABeltramo commented on GitHub (Nov 20, 2025): > I have it split currently to use my Intel Arc for encode and AMD for render. If I wanted to force Wolf to use just the AMD (renderD129) what is the best way to do this? Ideally you would just set `WOLF_RENDER_NODE=/dev/dri/renderD129` and that should be it. Unfortunately, since you have 2 VAAPI capable GPUs (Intel+AMD), there's currently an issue with that were a little part of our Gstreamer pipeline defaults to `/dev/dri/renderD128` messing everything up. Can you try something like the following? ```yaml services: wolf: image: ghcr.io/games-on-whales/wolf:stable environment: - WOLF_LOG_LEVEL=DEBUG - WOLF_RENDER_NODE=/dev/dri/renderD129 volumes: - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/input:/dev/input:rw - /mnt/udev:/run/udev:rw - /srv/wolf:/etc/wolf:rw device_cgroup_rules: - 'c 13:* rmw' devices: - /dev/dri/renderD129 - /dev/uinput - /dev/uhid restart: unless-stopped network_mode: host ``` The idea is that we only expose one GPU to Wolf (`/dev/dri/renderD129`) instead of the full `/dev/`. That will break DualSense joypad support (because it needs access to `/dev/hidrawX` devices, which is why we mount the full `/dev/`) but apart from that everything else should work. Let me know if that works for you! We've just recently fixed multi-GPU selection for Nvidia, the next one up is definitely Intel/AMD but no ETA yet..

bsakaguchi commented

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

Author

Owner

@jakepi84 commented on GitHub (Nov 20, 2025):

Hey @ABeltramo thank you again. Yes, forcing the device works without issue. I don’t have a DualSense, I just use a regular Xbox Series controller so it’s not an issue for me.

It is now using my AMD (renderD129) for both encode and render, not the end of the world.

@jakepi84 commented on GitHub (Nov 20, 2025): Hey @ABeltramo thank you again. Yes, forcing the device works without issue. I don’t have a DualSense, I just use a regular Xbox Series controller so it’s not an issue for me. It is now using my AMD (renderD129) for both encode and render, not the end of the world.

bsakaguchi commented

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

Author

Owner

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

Glad that fixes it, have fun!

@ABeltramo commented on GitHub (Nov 20, 2025): Glad that fixes it, have fun!