Closed alhirzel closed 4 years ago
Here's info on the workaround I have used: https://github.com/docker-library/postgres/issues/681#issuecomment-586811176
This looks like we just need to pin the version of postgres. For now until there is more detailed developer time to look at the workaround you suggest, can you test 9.6.16
and if that works we can pin it in the docker-compose?
Will POSTGRES_HOST_AUTH_METHOD: trust
work for older versions as well?
@alhirzel I'll have PR for you to look at in about a minute that uses the envar.
@alhirzel please test https://github.com/singularityhub/sregistry/pull/278. Thank you!
@vsoch #278 works great
okay let's get it deployed and built asap then! Thanks for catching this!
Fixed with #278. @alhirzel you can use the branch, and wait for the containers to pop up at https://quay.io/repository/vanessa/sregistry?tab=tags
Describe the bug
The following appears in
docker-compose logs
:To Reproduce
Attempt
docker-compose up
.