fix(docker): pin postgres image to 17

[itsalaidbacklife]

Summary

The packaged docker/docker-compose.yml pins the database service to postgres:latest. postgres:latest has advanced to PostgreSQL 18, which changed the container's data-directory layout and is incompatible with the existing /var/lib/postgresql/data bind mount — the database container crash-loops on start with:

Error: in 18+, these Docker images are configured to store database data in a format which is compatible with "pg_ctlcluster" ... there appears to be PostgreSQL data in: /var/lib/postgresql/data (unused mount/volume)

This makes npm run docker:start (and the packaged local DB) fail out of the box.

Fix

Pin the image to postgres:17, which uses the classic /var/lib/postgresql/data PGDATA and works with the current mount. Pinning also makes local DB runs reproducible.

Testing

• With postgres:latest: database container status is Restarting (1) in a loop (reproduced).
• With postgres:17: docker compose -f docker/docker-compose.yml up -d database → container Up, pg_isready passes, psql connects (PostgreSQL 17.10). Lifted the app against it in staging mode successfully.

Notes / follow-up

This restores the current behavior with minimal change. A larger follow-up could instead adopt the PG18 image guidance (mount a single volume at /var/lib/postgresql so pg_upgrade --link works) if the project wants to track the latest major — left out of scope here.

🤖 Generated with Claude Code