I use NextCloud via docker-compose.
After a recent docker-pull, Nextcloud was upgraded from 29 → 30.
However, this seems to have created an issue with the db-container coming up:
db_1 | 2024-10-04 20:27:20.365 UTC [1] FATAL: database files are incompatible with server
db_1 | 2024-10-04 20:27:20.365 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 16, which is not compatible with this version 17.0.
I was able to fix this by using postgres:16-alpine insted of postgres:alpine but I think it does not make sense to keep postgres16 in the long run?
Do I need to convert the db from postgres 16 to 17 e.g. via pgautoupgrade or what would you suggest?
FYI: 16 is well supported. 17 just came out. Also, 16 is the latest officially supported by Nextcloud (see system requirements).
Using at least a major version tag on image references to avoid surprise major version updates is good practice so sounds like you’re covered there now.
Do I need to convert the db from postgres 16 to 17 e.g. via pgautoupgrade or what would you suggest?
There is no need to bump to 17 unless you wish to (and are okay with it not being a supported configuration for Nextcloud). I haven’t used the pgautoupgrade image approach before. The official bits are all well documented: