mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #106] Steam container crashing after steam installation #71
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#71
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 @moracabanas on GitHub (Aug 30, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/106
Originally assigned to: @salty2011 on GitHub.
Issue description
I follow docker instructions. Every APP is working but Steam.
It shows a black screen, then I press Shift and it show this view, otherwise it remains at black screen
At this point here are the Steam container logs:
Then it installs like this
And it crashes after that inmediately.
Recurrent tries to open Steam from Moonlight client crashes Steam immediately with this.
There is no further logs available before crashing the Steam container.
I can reproduce from the ground up deleting
/etc/wolf/<number>/Steamdir.Things I have tried:
/etc/wolf/cfg/config.tomllike this (note mounts=""/run/dbus..."):"Privileged: true"but it doesn't workNo success.
Thoughts about this issue
I think there is something wrong with X11 in Popos so I cannot handle your compositor implementation without dummy HDMI plug or switching to Wayland(which I have no idea about)
The thing is, Firefox, Pegasus, Retroarch and the Ball Test are working with sound.
Further relevant info
S.O
GPU Resources
Nvidia Container CLI output
Nvicia SMI output
Thanks you for this impressive piece of software.
Regards
@salty2011 commented on GitHub (Aug 30, 2024):
Hey @moracabanas
Interesting issue you are getting. Could you also attach the docker compose config for reference. Thanks for providing all the other information.
Additionally i noticed the in the config.toml the steam container you are using is "ghcr.io/games-on-whales/steam:edge",
Have been chatting on the discord about this issue, the screen shots / logs you have posted indicate that the container doesn't start sway. Just to rule things out, on the host can you try pulling the steam image again using
docker pull ghcr.io/games-on-whales/steam:edge@moracabanas commented on GitHub (Aug 30, 2024):
Thanks for the suggestion I'm trying it out rn
Here is my
docker-compose.ymlBecause I am running a LLM on GPU0, I am trying to select GPU1 by forcing
D129rendering node selection, and I tested it working on firefox by checkingnvidia-smiusage.PD: While I am not proficent, I "speak fluent Docker"
@moracabanas commented on GitHub (Aug 30, 2024):
I've tried to repull the Steam image. Now I can see this before the container inmediately vanishes:
@ABeltramo commented on GitHub (Aug 30, 2024):
Ok so you had an old Steam image locally, have you tried Wolf in the past? Might be worth to update the wolf image too!
Could you also change the env variable
WOLF_LOG_LEVEL=DEBUGand post the full logs from when you start Wolf down to when Steam crashes?@moracabanas commented on GitHub (Aug 30, 2024):
You are right I have tried Wolf several months ago, and, because I was managing this workstation with Portainer, the images weren't updated by default.
Because I didn't remember I used it on the past, pulling all new images fixed it!
Now working as expected with some quirks!
Thanks you for your help
@salty2011 commented on GitHub (Aug 31, 2024):
Not a problem. Glad to see it working for you.