real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres LOG: provided user name (postgres) and authenticated user name (root) do not match
real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres FATAL: Peer authentication failed for user "postgres"
real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres DETAIL: Connection matched pg_hba.conf line 90: "local all postgres peer"
Seems to show that error even though works fine. Also can i not use bind mount instead of volume mount?When i compose down and up data seems to be gone.Does making bind mount not persist data as above
Generally it's not recommended to set a user as postgres, there is already a super user account for that. We might even prevent this specific username in future.
What is the bug or the crash?
real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres LOG: provided user name (postgres) and authenticated user name (root) do not match real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres FATAL: Peer authentication failed for user "postgres" real-db-1 | 2023-09-06 13:41:44.745 UTC [299] postgres@postgres DETAIL: Connection matched pg_hba.conf line 90: "local all postgres peer"
Steps to reproduce the issue
where .db_env
Versions
kartoza/postgis:15-3.4
Additional context
Seems to show that error even though works fine. Also can i not use bind mount instead of volume mount?When i compose down and up data seems to be gone.Does making bind mount not persist data as above