mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #129] WSL2 - Issues when running Wolf #82
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LanHikari22 on GitHub (Sep 28, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/129
Hi,
I was trying to set this up on WSL2 with Docker using the NVIDIA compose.yaml and also CLI approach from https://games-on-whales.github.io/wolf/stable/user/quickstart.html
I am able to confirm that docker has access to my NVIDIA GPU with
I then proceeded to try the following CLI command on WSL2 ubuntu22.04 as recommended for WSL2 in the quickstart:
This starts up, but I am not able to get much out of http://localhost:47989
And I'm also not able to pair Moonlight with it when I put localhost in moonlight It doesn't say anything. I'm not sure what the expected behavior is here.
Here is the log I get from starting up the docker container:
Thanks,
Mohammed
@LanHikari22 commented on GitHub (Sep 28, 2024):
Update.
This might have been related to me having another sunshine server running that I wasn't aware of and I shut down. I also noticed in the logs that it complained about the uid being used. In https://hub.docker.com/r/lizardbyte/sunshine they included PUID and GUID environmental variables, so I included them in my docker command as well. So I ran it with
And this time I was able to get moonlight to register Wolf on localhost. When it asked for a pin to pair on, I noticed the docker logs sent me a URL on port 47989 that I was able to access and complete the pairing. Then in Moonlight I was presented with multiple systems, I tried Firefox but it was a black screen and I also wasn't sure how to get out back into my system from that. Pressing many keys quickly seemed to have crashed the docker container.
The last of the logs on that was
I also see now that I can do (on Windows 11) Ctrl+Shift+Alt+x to toggle the moonlight stream out of fullscreen view then Windows to regain control over the mouse in my host environment.
The Test ball functions, but Firefox, Lutris, Pegasus, RetroArch, and Steam give black screens. The Quickstart did mention that a black screen will show up initially as Wolf needs to download data about the container, but I am not seeing any Download indications in the Wolf docker logs or in the WolfFirefox_... container. I can see in https://github.com/games-on-whales/wolf/issues/73#issuecomment-2149031219 that this is not yet implemented or easy to, but so far, nothing seems to change the black screen as I wait.
When running firefox, it remains in black screen for a long time. The Wolf docker logs show very long trace logs that if I type on the keyboard lead them to freeze and I no longer can move the mouse in the firefox black screen moonlight stream:
The WolfFirefox container has these logs in the end suggesting it's already started firefox though I still have a black screen:
240928 WolfFirefox Docker Logs.txt
Here are also some logs for the Wolf docker container when sometimes the Firefox container crashes and it complains about failing to load driver like kms_swrast:
240928 Wolf logs on Firefox Crash 1.txt
So is this not intended to be used in a general purpose desktop environment way?
Thanks,
Mohammed
@ABeltramo commented on GitHub (Sep 28, 2024):
Hi Mohammed,
From the details that you've provided you have quite a few issues 😅
You are running Wolf under WSL2 and as the docs clearly points out, this is experimental and not properly tested.
With that said, you also have a few issues just by looking at your logs:
This means that you are missing HW acceleration, AKA your GPU is not being picked up by Wolf and that will cause issues later on when trying to start our virtual displays. From the commands that you have posted above you are clearly missing the Nvidia specific Docker flags that are needed in order to activate HW acceleration
If you have the Docker Container Toolkit installed and it's at version >=
1.16.0(please see the docs on how to check this) you'll have to add at the very least:Then you added two env variables because you saw it somewhere else
This can only work if the user
1000can access the Docker socket, if you rundockerusingsudo(which is the default installation) you should remove those.If you still run into troubles after all this (very likely given other reports on Discord for WSL2) feel free to post your full logs under this issue: https://github.com/games-on-whales/gow/issues/13