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
When i do docker compose down the server is killed without the server saving its state. Is there any way that it can detect the SIGTERM signal and save the state immediately?
The text was updated successfully, but these errors were encountered:
mmonj
changed the title
SIGKILL / SIGTERM detection
SIGTERM detection
Jul 27, 2024
The problem isn't the signal, all relevant signals are properly passed through to the server process. The problem is very likely that your Docker daemon kills the container before the Valheim server can save the world to disk because the default timeout is 10s. That's why the docs say to start the container with --stop-timeout 120.
I just got passed an issue where state was not saving upon docker stop, even with proper timeouts, in an Azure ubuntu 24 VM, once I rolled back to ubuntu 22, it worked again, I didn't get the chance to investigate further tho.
I monitored the logs after docker stop and got nothing, container wouldn't log anything and then would just exit.
When i do
docker compose down
the server is killed without the server saving its state. Is there any way that it can detect the SIGTERM signal and save the state immediately?The text was updated successfully, but these errors were encountered: