Open JCionx opened 1 month ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
+1 to this.
Yeah it looks busted, the namespace stuff can be worked around with seccomp and apparmor unconfined.(bubblewrap support) But now it looks like the Steam web helper crashing is blocking. It just core dumps for me, and unfortunately I do not have a lot of options here with steam being closed source.
I suspect valves pinned repos might be out of sync with head arch to the point that it is breaking steam installed from that same repo. When I get time I will try to make a base image pinned to steamOS repos only and see if that fixes anything up.
So I built a couple variants out from Valve's 3.5, 3.6, and staging repos. Unfortunately their repos lack a bunch of Intel and AMD drivers as it is scoped to the deck and modern RDNA3 stuff, so that drops the broader GPU compatibility. I was hoping it would be a silver bullet, but it looks like this repo will most likely be sunset as I don't have a way to package a general compatible SteamOS image which was the whole point of it in the first place.
I'm sorry to hear that. Hopefully there will be a fix for this issue in the future. Every image that I have tried seems to be broken as well...
I don't know if it relates, but I've been having issues with Steam, even on my regular (i5-14600K) desktop. Sometimes Steam crashes, games such as Terraria "randomly" freeze and crash the window manager, and Steam's UI becomes unresponsive and laggy all the time. It's been quite unstable, and I can't blame the CPU since everything else works well. Perhaps it could be helpful to reach Steam directly to get the whole driver/compatibility situation resolved? I feel like the issues with the client and the docker image might be related somehow. I can't really debug it since, like you said, it's proprietary software.
Games use bubblewrap (proton and linux runtime isolated in a container like docker) and do not have host deps unless they are mounting in video card drivers. This is actually breaking the steam client, specifically the steam web helper. I can get something semi working using the staging repos if you have an RDNA3 card, but I can't have an image where 90% of users will get an error on their hardware. Too much support, I'll ponder for a couple weeks before officially shutting it down.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
After installing the docker container and opening it up, I'm greeted with this Steam error:
Expected Behavior
I expected Steam to launch normally.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs