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
#4 works completely fine, but I won't go into detail into it as there are heaps of files involved. If any of you would like to have it, feel free to ask.
I have tested this with both 14-master and 13-master.
Being able to access psql from the container is very important as you will need this capability to export and import [very large] databases.
The text was updated successfully, but these errors were encountered:
Thanks for chiming in. Prior to your comment, I have tried everything of those you have already outlined, some not really 100% relevant except for pinning the version. I have to say for some reason that worked when I paid very close attention to the user/group ownership of the socket. I must have indeed just missed a few things. Thanks, closing issue now.
When using the image with Docker Compose and accessing it with
docker exec -it <container name> bash
andpsql
, you will get this error message:I have tried to isolate the problem with the following:
docker run
to test and see if I can runpsql
just finedocker-compose.yml
of mine and psql sports the error.For #1, I ran the following command:
Running
psql
just works fine.I won't go into detail with #2 as #3 might be more interesting. For #3, I had the following docker-compose.yml:
#4 works completely fine, but I won't go into detail into it as there are heaps of files involved. If any of you would like to have it, feel free to ask.
I have tested this with both
14-master
and13-master
.Being able to access psql from the container is very important as you will need this capability to export and import [very large] databases.
The text was updated successfully, but these errors were encountered: