Segmentation fault on container startup #1131
Unanswered
RemotelySensed
asked this question in
Help!
Replies: 1 comment 3 replies
-
|
Hey thats very strange, ive never seen a seg fault from steamcmd like that. What processor do you have? what memory do you have? have you tried restarting and updating the host before re-running? A seg fault like that indicates an issue with the memory it was trying to use and since i don't have any insights into the script itself. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
System Information
Issue Description
I'm fairly new to Docker and learning as I go, so please forgive any obvious mistakes. I am having Segmentation fault errors during the initiation of the steam client phase of container startup.
Issuing
docker-compose up --detachseems to open the container properly, and it starts to launch the server. It checks for updates and downloads as needed. Once that's done, it launches steamcmd, and displays the Steam clients version info. The Segmentation Fault error comes in once the steamcmd.sh is executed. (log file below)As user/group info don't match the typical linux ones, I had tried adding mine into the yml file with PUID=501 and PGID=20 (but that ends up with folder permissions error when trying to create/access the folder I have the yml file in.
Any guidance or directions to look would be greatly appreciated. Thanks in advance.
Logfile:
Beta Was this translation helpful? Give feedback.
All reactions