Can't replace pg_hba.conf when create my custom container

[rimelek (Ákos Takács)]

Is it a task at school? If you are just practicing that’s fine, otherwise I answered in the other topic how you should trust (usually you should not) in all hosts

My changes were lost in new Docker container

UPDATE I was wrong. The entrypoint just appends a line, it will not reset the file, but it is on a volume so when you commit the container, that will not be committed ince that is not part of the container. The rest of my old answer is correct. You should not change the file, but use POSTGRES_HOST_AUTH_METHOD, but the bets if you don’t trust in every host without a password unless you are just testing on your local computer. My original answer is below The entrypoint overwrites that file eve…

Since I gave you the wrong reason why the changes were lost, I updated my answer.

@asubscriber

But the container is not started.

An error message (docker logs CONTAINERNAME) and the whole content of the config would be helpful, but I guess you copied the file with wrong permissions. Make sure the postgresql user can read and write it but nobody else.

8.0K -rw-------  1 postgres postgres 4.5K Feb 15 19:06 pg_hba.conf