Open jammsen opened 2 years ago
Automatic scheduled restarts are certainly a possibility, but have you considered or tried limiting the container's resources instead?
Eg. you could limit it to only a certain amount of memory and to only use a certain amount of cores.
To limit with the Docker runtime, see here. Basic usage example would be something like --memory=8g --cpus=4.0
, which would limit the container to 8GB of memory and 4 cores (or 400% CPU).
Hey @Dids, thanks for the reply.
( To be honest i looked into the "docker run reference" page - https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources - So thanks for sharing that other link )
Yes i thought about ressource limitation, but i didnt apply it because some other dedicated server admins and the Mod Developer of Darkness Falls (very popular mod - https://dev.azure.com/KhaineUK/_git/DarknessFallsA20 ) seemed pretty knowledgable and confirmed that 7dtd has many memory leaks. In my mind the limitation would rather make the server more unstable with random kills than, on the other hand, the restart would help to clean up the mess, i really hope you understand my point here 😅 (having a bit of a hard time).
If you can give me your Discord-ID or a more private email i can post you the content/log, but its a bit "rough tone" and i would favor it to not post that on github in the public 😅
@Dids a penny for your thoughts.
Hey @Dids since this (20.4) and the last version (20.3) of 7dtd the memory leaks are heavily increasing. My server sometimes tries to allocate 73GB in a 32GB vm and therefore crashes. Reinstalling (start from scrap) and all didnt help in testing. But rebooting every like 24 hours is fine, to normalize memory usage.
Question: Maybe it would be an idea to extend the scheduler node app for a "Set Intervall" for restarts, conrtrolled by a Docker Environment variable?