~/repos/code-review @19a083ac !2 ❯ docker compose up
[+] Running 3/3
✔ Network code-review_default Created 0.0s
✔ Container code-review-db Created 0.0s
✔ Container code-review-backend Created 0.0s
Attaching to code-review-backend, code-review-db
code-review-db | Error: in 18+, these Docker images are configured to store database data in a
code-review-db | format which is compatible with "pg_ctlcluster" (specifically, using
code-review-db | major-version-specific directory names). This better reflects how
code-review-db | PostgreSQL itself works, and how upgrades are to be performed.
code-review-db |
code-review-db | See also https://github.com/docker-library/postgres/pull/1259
code-review-db |
code-review-db | Counter to that, there appears to be PostgreSQL data in:
code-review-db | /var/lib/postgresql
code-review-db |
code-review-db | This is usually the result of upgrading the Docker image without
code-review-db | upgrading the underlying database using "pg_upgrade" (which requires both
code-review-db | versions).
code-review-db |
code-review-db | The suggested container configuration for 18+ is to place a single mount
code-review-db | at /var/lib/postgresql which will then place PostgreSQL data in a
code-review-db | subdirectory, allowing usage of "pg_upgrade --link" without mount point
code-review-db | boundary issues.
code-review-db |
code-review-db | See https://github.com/docker-library/postgres/issues/37 for a (long)
code-review-db | discussion around this process, and suggestions for how to do so.
code-review-db exited with code 1
Presumably related to #3555?