docker-library / docker-library/postgres
Can not configure custom authorization at pg_hba.conf because of more global rule
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
docker-entrypoint.sh sets up host all all all scram-sha-256 into pg_hba.conf file.
https://github.com/docker-library/postgres/blob/8a631b939a0b4197cb6bef49b50b6c40c80ddf5b/15/bookworm/docker-entrypoint.sh#L252
For my database located in trusted network I wan to configure trusted authentication, but can not, because first list matched first:
...
host all all all scram-sha-256
host db user 172.16.0.0/12 trust
My /docker-entrypoint-initdb.d/000-trust.sh script is:
echo "host db user 172.16.0.0/12 trust" >> "${PGDATA}/pg_hba.conf"
It would be nice if this catch-all rule you will add later after processing init files
https://github.com/docker-library/postgres/blob/8a631b939a0b4197cb6bef49b50b6c40c80ddf5b/15/bookworm/docker-entrypoint.sh#L331
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-entrypoint.sh around the pg_hba.conf setup at lines 252 and 331, and review how /docker-entrypoint-initdb.d/ scripts are processed. Confirm the ordering that causes the catch-all scram-sha-256 rule to match first; done means trusted rules added by initialization scripts can take effect without breaking the default authentication setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql, shell
- Domain
- database, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100