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
I am unable to authenticate to my postgresql database using environment variable PGPASSFILE to point to a file containing the password for my database. Storing the same password in the environment variable PGPASSWORD surprisingly works.
PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps; instead consider using a password file (see Section 34.16).
PGPASSFILE behaves the same as the passfile connection parameter.
Hi,
First off, this might be an upstream bug, unsure.
I am unable to authenticate to my postgresql database using environment variable
PGPASSFILE
to point to a file containing the password for my database. Storing the same password in the environment variablePGPASSWORD
surprisingly works.These two environment variables are defined in the postgres docs for env vars
password file documentation: https://www.postgresql.org/docs/16/libpq-pgpass.html
There is a foot note that the file it self needs to have access mode 0600 which docker can do with
mode
parameter in secrets-blockExample environment (using Docker compose!)
docker-compose.yml
coredns.pgpass
Logs:
The text was updated successfully, but these errors were encountered: