Skip to content

Conversation

@alessandromarchetti
Copy link

Your checklist for this pull request

  • I've read the contributing guideline.
  • I've tested my changes by building and running mquery, and testing changed functionality (if applicable)
  • I've added automated tests for my change (if applicable, optional)
  • I've updated documentation to reflect my change (if applicable)

What is the current behaviour?
Currently, the docker-compose.yml file doesn't specify a PostgreSQL version, defaulting to 'latest'. With PostgreSQL 18's recent release, this causes container startup failures due to a changed data directory path from /var/lib/postgresql/data to /var/lib/postgresql.

What is the new behaviour?

  • Added explicit version control for PostgreSQL in docker-compose.yml
  • Set PostgreSQL 17 as the default version to maintain stability
  • Added environment variables to control PostgreSQL version and data path
  • This prevents the startup failure by ensuring compatibility with the mounted volumes

Closing issues
fixes #456

@alessandromarchetti alessandromarchetti force-pushed the fix/docker-compose-postgres-tag branch from 938f925 to f0a348c Compare September 29, 2025 15:04
@alessandromarchetti alessandromarchetti changed the title Added configurable postgres tag and dst mount path Added configurable postgres tag and dst mount path to the docker compose Sep 29, 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.

Docker compose - Postgres container creation fails: error mounting data volume

1 participant