Does not work with official postgres:10 ( or earlier ) due to pg_hba.conf

[EugenMayer]

When using your image to migrate the databases, pg_hba.conf will be replaced using a version, which will not allow other hosts to connect using a password

this line is not included in the pg_hba.conf of the newly migrate DATA folder, lets assume pg11

host all all all md5

One can easily copy this file from pg10/data/pg_hba.conf to pg10/data/pg_hba.conf or just add the line i mentioned - but we might also consider mention this in the readme.

Without that, PG boots up just fine, the migratoin did work just fine - just no other service in the docker stack can use PG since they cannot connect to it :)

[tianon]

I think this might technically be a "duplicate" of #1 😅

(Although perhaps now closer to being realistic for fixing via docker-library/postgres#496!)

[EugenMayer]

Maybe add a "known issues" in the readme adding this note, since i ran into this backwards, wasted a bit of time to find out why the server is "not working" - great to see the complex bootstrap components being split up into reusable chunks.

[EugenMayer]

For anybody, just a quickfix: After starting your new ( upgraded ) db and it complains about the missing entry, just exec into the postgresql container and run

 echo "host all all all md5" >> /var/lib/postgresql/data/pg_hba.conf

and restart the postgresql container

[inspiraller]

What if you are using replication, via docker stack deploy and want to have the same logic across instances?

[tianon]

You'll need to make your own (possibly derivative) image as your needs have advanced beyond the very basic proof of concept this repository contains.