[postgres] Issue with the mounting point

[guzmud]

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

1. OS: Windows
2. Runner: podman
3. OpenAEV-Platform/docker version: master

Reproducible Steps

Steps to create the smallest reproducible scenario:

1. Down any currently running OpenAEV docker stack
2. Delete previously existing docker volumes
3. 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

[guzmud]

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]

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.