I use docker compose on ubuntu. Had updated from an older version to 1.137.0 when it was new and left it assuming all was fine. It wasn't. Server is constantly restarting and I would appreciate some help with this as I don't want to blindly update to latest in case it causes further issues.
What is the issue/solution for this issue, can I resume upgrading towards 2.2?
Side questions, asside from upgrading immich, when should redis/postgres be upgraded with newer images?
1:C 07 Nov 2025 19:14:06.593 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo1:C 07 Nov 2025 19:14:06.593 # Redis version=6.2.16, bits=64, commit=00000000, modified=0, pid=1, just started1:C 07 Nov 2025 19:14:06.593 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf1:M 07 Nov 2025 19:14:06.593 * monotonic clock: POSIX clock_gettime1:M 07 Nov 2025 19:14:06.838 * Running mode=standalone, port=6379.1:M 07 Nov 2025 19:14:06.838 # Server initialized1:M 07 Nov 2025 19:14:06.838 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.1:M 07 Nov 2025 19:14:06.861 * Ready to accept connections
1:C 07 Nov 2025 19:14:06.593 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo1:C 07 Nov 2025 19:14:06.593 # Redis version=6.2.16, bits=64, commit=00000000, modified=0, pid=1, just started1:C 07 Nov 2025 19:14:06.593 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf1:M 07 Nov 2025 19:14:06.593 * monotonic clock: POSIX clock_gettime1:M 07 Nov 2025 19:14:06.838 * Running mode=standalone, port=6379.1:M 07 Nov 2025 19:14:06.838 # Server initialized1:M 07 Nov 2025 19:14:06.838 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.1:M 07 Nov 2025 19:14:06.861 * Ready to accept connections