Timeline for Docker-compose environment variables
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 14, 2022 at 0:13 | vote | accept | royalaid | ||
| Jun 24, 2021 at 11:07 | answer | added | ewulff | timeline score: 3 | |
| Oct 13, 2020 at 21:31 | answer | added | Aditi Lamkhede | timeline score: 7 | |
| Oct 6, 2020 at 13:52 | answer | added | Crt Mori | timeline score: 12 | |
| Jan 7, 2020 at 15:26 | answer | added | Abdelsalam Megahed | timeline score: 50 | |
| Aug 31, 2017 at 18:09 | answer | added | Alexey | timeline score: 24 | |
| Jun 23, 2017 at 18:45 | answer | added | Bryan | timeline score: 1 | |
| Feb 4, 2017 at 17:58 | answer | added | davetapley | timeline score: 102 | |
| Sep 30, 2016 at 6:06 | comment | added | jap1968 |
I am experiencing a very similar problem. I have done the necessary changes in pg_hba.conf to allow remote connections. The problem seems to be docker-compose being ignoring the environment variable POSTGRES_PASSWORD
|
|
| Apr 28, 2015 at 5:43 | vote | accept | royalaid | ||
| S Feb 14, 2022 at 0:13 | |||||
| Apr 12, 2015 at 22:13 | answer | added | Greg | timeline score: 24 | |
| Apr 11, 2015 at 18:54 | comment | added | Daniel Vérité |
@db implies a remote connection and nothing suggests you've allowed them in postgresql.conf and pg_hba.conf, especially the last one. It doesn't make sense to not include directly the auth error message in this question.
|
|
| Apr 11, 2015 at 17:25 | review | First posts | |||
| Apr 11, 2015 at 17:27 | |||||
| Apr 11, 2015 at 17:24 | history | asked | royalaid | CC BY-SA 3.0 |