stable/16: Wrong pgsql version in docker-compose.yml #113

Activity

1. davemc50 commented on Sep 16, 2025

   

   davemc50

   on Sep 16, 2025

   More actions

   This is still an issue, and a trivial fix, how come such a straightforward issue sits open for six months?

   👍React with 👍4Reacted by Malachi Bergman, Iceflower, Keanu Dölle and Julian Dumitrascu
2. Tofandel commented on Oct 14, 2025

   

   Tofandel

   on Oct 14, 2025

   More actions

   It should even be 17

   👍React with 👍1Reacted by Waleed Mortaja
3. nWacky commented on Dec 8, 2025

   

   nWacky

   on Dec 8, 2025

   More actions

   For existing installations, Postgres data needs to be migrated before the version can be changed from 13 to 16.
   https://www.openproject.org/docs/installation-and-operations/misc/migration-to-postgresql17/

   Probably that's why the Postgres version in docker compose is old.

   It would be nice to have a recent recommended Postgres version in docker compose by the default, though
4. area51tazz commented on Jan 9, 2026

   

   area51tazz

   on Jan 9, 2026

   More actions

   Can we just change it to 17 for new installations? Other than the migration commands, I can't remember anything special about updating the docker compose file before pulling it.
5. Tofandel commented on Jan 12, 2026

   

   Tofandel

   on Jan 12, 2026

   Last edited by Tofandel

   More actions

   You can with a docker-compose.override.yml file, if you already migrated your data to postgres 17 or for a new installation

   services:
     db:
       image: postgres:17
       environment:
         POSTGRES_USER: openproject
     # If you don't need the nginx reverse proxy
     proxy:
       profiles:
         - donotstart

   This file is gitignored, so it will survive a git pull. This is the proper way to make customisations to the docker compose file