-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Steam now requires user namespaces to be enabled #15
Comments
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. |
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. |
So I built a couple variants out from Valve's 3.5, 3.6, and staging repos. |
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 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. |
I have the same issue on a 5800H MiniPC with Ubuntu 24.04.1 LTS (Noble Numbat) also using CasaOS. Any way to correct it? |
I still have the same problem. It seems to be a problem with Steam. |
I wonder if there is a way to force a specific version of steam to install and run... |
Have you had a look at this? |
I'm also getting this error |
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
The text was updated successfully, but these errors were encountered: