SIGTERM triggers non-zero exit code

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. • Yes The bug Reopening of It is very common indeed to exit with 0 when gracefully handling SIGTERM. Specifically because systems like Quadlets as well as Kubernetes treat non-zero codes as an error. > Are you sure an exit code 0 on SIGTERM is the correct behaviour? Just as a basic thing to try, if I SIGTERM a sleep command it exits with that same code 143: This is shell specific. Because sleep does not actually handle SIGTERM and so the default Linux behavior is taken. > Are you sure they're actually getting a SIGTERM? A cursory look through the docker-library/postgres issues suggests they may be turning those into SIGINT instead. Yes, redis for example exits with zero on receiving SIGTERM. [Syncthing as another example]( The OS that Immich Server is running on Linux Version of Immich Server v2.7.5 Version of Immich Mobile App • Platform with t…