You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before 9b4b400, docker-compose.yml specified an unversioned tag (alpine) for the PostgreSQL image. When I deployed Manifold v4.1.2 with it, postgres:alpine was equivalent to postgres:12-alpine. Commit 9b4b400, merged into v5.0.0, specified postgres:11-alpine, so upgrading to Manifold v5.0.0 effects a downgrade of the Postgres database, and Postgres refuses to work with the existing data. From the service logs:
PostgreSQL Database directory appears to contain a database; Skipping initialization
[1] FATAL: database files are incompatible with server
[1] DETAIL: The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 11.8.
I solved this for myself by patching docker-compose.yml to reference postgres:12-alpine. Would that be acceptable?
The text was updated successfully, but these errors were encountered:
Before 9b4b400,
docker-compose.yml
specified an unversioned tag (alpine
) for the PostgreSQL image. When I deployed Manifold v4.1.2 with it,postgres:alpine
was equivalent topostgres:12-alpine
. Commit 9b4b400, merged into v5.0.0, specifiedpostgres:11-alpine
, so upgrading to Manifold v5.0.0 effects a downgrade of the Postgres database, and Postgres refuses to work with the existing data. From the service logs:I solved this for myself by patching
docker-compose.yml
to referencepostgres:12-alpine
. Would that be acceptable?The text was updated successfully, but these errors were encountered: