Skip to content

Conversation

@stevensJourney
Copy link
Collaborator

A minor followup to #55.

This adds a changelog entry for the relevant changes, including some basic instructions for potential demo users.

This also fixes the major version of the Postgres image to the floating 18 tag.

mattgallagher92 and others added 3 commits November 24, 2025 16:45
This is to resolve errors like the following, now that postgres:latest
resolves to the v18 image by default.

```quote
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.

See also docker-library/postgres#1259

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.

See docker-library/postgres#37 for a (long)
discussion around this process, and suggestions for how to do so.
```
@Chriztiaan
Copy link

Changelog covers both scenarios to my liking. I think it would be useful to have the clean slate explanation as a general entry in the readme, but maybe that's a case of documenting how Docker works.

@stevensJourney stevensJourney merged commit e217e11 into main Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants