Closed UmutAlihan closed 9 months ago
Don't use supervisorctl to start steam unless you are running outside of the Steam Headless desktop.
Don't run Steam as root with sudo. It will just create a steam config in /root
which will be blown away the next time you update the container.
Update your docker-copose.yaml with the latest template found in this project's documentation. It is no longer recommended to use a macvlan network.
Join us on Discord for support. This is not a bug.
Describe the Bug
I start the steam using "supervisorctl start steam".
But it otuputs no logs, I see only err.log as below:
Steam is not starting but when I check "ps aux | grep steam" I see steam related processes:
If I execute "sudo /usr/games/steam" it starts but even though steam is installed, it attempts to install new steam into "root" home:
I installed steam as it asked me to do it:
After installation and update; Steam WebUI starts but after starting a game, the game crashes after a couple of seconds or interactions. I will not give the details of the crash issue here because I assume that is for another issue. Currently I am wondering why supervisor steam service is not able run steam as it is.
Any help is much appreciated. Many thanks for such great repository btw. It is a wonderful contributioun to the community. Cheers,
Steps to Reproduce
No response
Expected Behavior
I was expecting that steam launches and start gaming flawlessly without any crash :'/
Screenshots
No response
Relevant Settings
docker-copose.yaml:
.env:
Version
Pulled latest docker image as of 25.09.2023
Platform
Relevant log output