plandex-postgres-1 exited with code 1 (restarting)
plandex-postgres-1  | Error: in 18+, these Docker images are configured to store database data in a
plandex-postgres-1  |        format which is compatible with "pg_ctlcluster" (specifically, using
plandex-postgres-1  |        major-version-specific directory names).  This better reflects how
plandex-postgres-1  |        PostgreSQL itself works, and how upgrades are to be performed.
plandex-postgres-1  |
plandex-postgres-1  |        See also https://github.com/docker-library/postgres/pull/1259
plandex-postgres-1  |
plandex-postgres-1  |        Counter to that, there appears to be PostgreSQL data in:
plandex-postgres-1  |          /var/lib/postgresql/data (unused mount/volume)
plandex-postgres-1  |
plandex-postgres-1  |        This is usually the result of upgrading the Docker image without
plandex-postgres-1  |        upgrading the underlying database using "pg_upgrade" (which requires both
plandex-postgres-1  |        versions).
plandex-postgres-1  |
plandex-postgres-1  |        The suggested container configuration for 18+ is to place a single mount
plandex-postgres-1  |        at /var/lib/postgresql which will then place PostgreSQL data in a
plandex-postgres-1  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
plandex-postgres-1  |        boundary issues.
plandex-postgres-1  |
plandex-postgres-1  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
plandex-postgres-1  |        discussion around this process, and suggestions for how to do so.