Closed scooper1 closed 2 years ago
Thank you for reporting an error and providing logfiles. Could you be so kind and fill out the information asked in the template that should open when you report here an issue (bug). This makes it much easyier for me.
What do you mean with: "I have tried setting user name with --user" ? You don't have to change anything on the user. In the container everything is setup as needed.
In general: I guess this is not a container problem. It works on many servers from N0ri, Dustin and me, also on many other servers from admins (I unfortunately didn't have the opportunity to be in contact with all of them :) . From the logfiles I expect that there is an issue with the mounting path. This would explain "(Read-only file system)". If only the coresponding files are correctly mounted into the container, then the error would be something else. Unless of course it is related to your setup that may have a problem with the container or since the last update we have some problem in the container that was not triggered on our servers.
As soon as you provide me the detail information I will try to troubleshoot and help you to get it running. Thank you very much for your cooperation in advance
in the end, i created a steam user and moved the files to that user and changed the owner to root:root
I have tried setting user name with --user but that just gives error user does not exist the problem appears to be container trying to write back to volumes with steam user
have you suggestions on how to fix these errors