This is the response when I try to run wasp db start on my Mac
Status: Downloaded newer image for postgres:latest Error: in 18+, these Docker images are configured to store database data in a format which is compatible with "pg_ctlcluster" (specifically, using major-version-specific directory names). This better reflects how PostgreSQL itself works, and how upgrades are to be performed.
Counter to that, there appears to be PostgreSQL data in: /var/lib/postgresql/data (unused mount/volume)
This is usually the result of upgrading the Docker image without upgrading the underlying database using "pg_upgrade" (which requires both versions).
The suggested container configuration for 18+ is to place a single mount at /var/lib/postgresql which will then place PostgreSQL data in a subdirectory, allowing usage of "pg_upgrade --link" without mount point boundary issues.
This is a pretty large breaking change, which is why this only makes the change in 18+ (which is currently in pre-release stages, and not due for GA until September, and pre-release PGDATA director...
There doesn't seem to be a good way to upgrade between major versions of postgres. When sharing the volume with a new container with a newer version of postgres it won't run as the data dir...
The Postgres 18 docker image contains changes to make it easier to upgrade which break our existing setup. See docker-library/postgres#37 for a long discussion of the issues being addressed. This ...