feat: update docker pgdata volume for postgres 18 #749
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
With postgres 18, the way pgdata volume is set has changed. docker-library/postgres#1259
db-1 | Error: in 18+, these Docker images are configured to store database data in a db-1 | format which is compatible with "pg_ctlcluster" (specifically, using db-1 | major-version-specific directory names). This better reflects how db-1 | PostgreSQL itself works, and how upgrades are to be performed. db-1 | db-1 | See also https://github.com/docker-library/postgres/pull/1259 db-1 | db-1 | Counter to that, there appears to be PostgreSQL data in: db-1 | /var/lib/postgresql/data (unused mount/volume) db-1 | db-1 | This is usually the result of upgrading the Docker image without db-1 | upgrading the underlying database using "pg_upgrade" (which requires both db-1 | versions). db-1 | db-1 | The suggested container configuration for 18+ is to place a single mount db-1 | at /var/lib/postgresql which will then place PostgreSQL data in a db-1 | subdirectory, allowing usage of "pg_upgrade --link" without mount point db-1 | boundary issues. db-1 | db-1 | See https://github.com/docker-library/postgres/issues/37 for a (long) db-1 | discussion around this process, and suggestions for how to do so. db-1 exited with code 1 (restarting)