You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment (please complete the following information):
OS: Fedora Linux 37 (Server Edition)
Docker: 23.0.1
Additional context
I've attempted to fix this issue multiple times but have had no luck so far. Apparently the docker exit code 137 is related to memory issues but I've checked to see if it runs out of memory and it doesn't seem to do so. I've never gotten it to start up on this machine.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
Rust server crashes, usually during asset warm up. Exit code 137, OOMKilled is false.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Rust server attempts to start, then crashes without any error or exit message shown in logs.
Screenshots
container-logs.txt
Environment (please complete the following information):
Additional context
I've attempted to fix this issue multiple times but have had no luck so far. Apparently the docker exit code 137 is related to memory issues but I've checked to see if it runs out of memory and it doesn't seem to do so. I've never gotten it to start up on this machine.
The text was updated successfully, but these errors were encountered: