Repository navigation
[postgres] Issue with the mounting point #123
Description
Description
Starting the docker stack from scratch leads to a pgsql failure: ✘ Container xtm-pgsql-1 Error dependency pgsql failed to start 2.1s.
This may be linked to docker-library/postgres#1409 and a recent update of the pgsql docker images. Screenshots and suggested fix can be found at the bottom of this issue.
Environment
- OS: Windows
- Runner: podman
- OpenAEV-Platform/docker version:
master
Reproducible Steps
Steps to create the smallest reproducible scenario:
- Down any currently running OpenAEV docker stack
- Delete previously existing docker volumes
podman compose -f .\docker-compose.yml up -d
Expected Output
Works
Actual Output
Fails on pgsql
Additional information
Output of the podman compose
Log details
Suggested fix
Following the details provided by the error message, replace /var/lib/postgresql/data with /var/lib/postgresql
Output of the podman compose after fix
Reacted by kerkyra3744
Activity
guzmud commentedon May 5, 2026
Nota bene: I have no idea (a.k.a. haven't take the time) how to handle this change for a on-going stack (a.k.a. do a proper migration), so the suggested fix may be useless for on-going production deployment
GaetanSantucci commentedon May 25, 2026
For Postgres V18, a dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. Release notes
Issue linked
On openaev repository #123
After some investigation, it appears that this resulted in breaking changes and without providing a clear migration path for our users.
We will work on resolving this and, in the meantime, revert to V17.
Here is a detailed documentation explaining the ins and outs.