…ker.com/_/postgres)

Important Note: (for PostgreSQL 17 and below) Mount the data volume at /var/lib/postgresql/data and not at /var/lib/postgresql because mounts at the latter path WILL NOT PERSIST database data when the container is re-created. The Dockerfile that builds the image declares a volume at /var/lib/postgresql/data and if no data volume is mounted at that path then the container runtime will automatically create an anonymous volume that is not reused across container re-creations. Data will be written to the anonymous volume rather than your intended data volume and won't persist when the container is deleted and re-created.

Remove redundant Layers:
- ENV defined as already part of the official image
- VOLUME is already defined in official image

- RUN PGDATA is performed by entrypoint of official image

- introduce lock file to prevent multiple backups running in the same time
- create full backup for versions with old schema
- write backup file to local config instead of relying on absolute path

- use new PGDATA schema that will be introduced in Postgresql18
- use build args for easy version adjustments

- use modular migrations scripts that are called during initialization of the database within the entrypoint of postgresql or run them manually for minor upgrades
- use util functions from docker-entrypoint.sh