[bitnami/postgresql] container refuse to start after upgrade

[jtremesay]

Name and Version

bitnami/postgresql:17.4.0

What architecture are you using?

amd64

What steps will reproduce the bug?

1. start a bitnami/postgres:16 container
2. upgrade to bitnami/postgres:17 using the upgrade instructions https://github.com/bitnami/containers/tree/main/bitnami/postgresql#upgrade-this-image

What is the expected behavior?

The upgraded container start without error

What do you see instead?

freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.67 INFO  ==> Welcome to the Bitnami postgresql container
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.67 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.67 INFO  ==> Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami/ for more information.
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.67 INFO  ==> 
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.68 INFO  ==> ** Starting PostgreSQL setup **
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.69 INFO  ==> Validating settings in POSTGRESQL_* env vars..
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.70 INFO  ==> Loading custom pre-init scripts...
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.70 INFO  ==> Initializing PostgreSQL database...
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.71 INFO  ==> pg_hba.conf file not detected. Generating it...
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.71 INFO  ==> Generating local authentication configuration
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.72 INFO  ==> Deploying PostgreSQL with persisted data...
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.73 INFO  ==> Configuring replication parameters
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.75 INFO  ==> Configuring fsync
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.75 INFO  ==> Configuring synchronous_replication
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.76 INFO  ==> Loading custom scripts...
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.76 INFO  ==> Enabling remote connections
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.77 INFO  ==> ** PostgreSQL setup finished! **
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | 
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | postgresql 09:43:10.78 INFO  ==> ** Starting PostgreSQL **
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | 2025-04-02 09:43:10.794 GMT [1] FATAL:  database files are incompatible with server
freshrss_postgresql.1.xkgozf959zhl@edemaruh    | 2025-04-02 09:43:10.794 GMT [1] DETAIL:  The data directory was initialized by PostgreSQL version 16, which is not compatible with this version 17.4.

Additional information

No response

[javsalgar]

Hi!

In this case you are upgrading between major versions of PostgreSQL, so you may need to dump the contents of the database and then restore them in the new image.

https://www.postgresql.org/docs/current/backup-dump.html