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 know why this is happening, but I'm looking for workaround recommendations.
I have psql running inside of a docker container that's accessible on the docker host at localhost:5432. Looks like wal-e is looking for the socket on my host at /run/postgresql/.s.PGSQL.5432, which of course doesn't exist (it does in the container). Would you recommend that I use volumes to expose this socket on my host? Or is there better way to run wal-e on a docker host on a PG instance that's running inside of a container?
I have no trouble connecting with:
$ psql postgres://user:password@localhost:5432
The text was updated successfully, but these errors were encountered:
I know why this is happening, but I'm looking for workaround recommendations.
I have
psql
running inside of adocker
container that's accessible on the docker host atlocalhost:5432
. Looks likewal-e
is looking for the socket on my host at/run/postgresql/.s.PGSQL.5432
, which of course doesn't exist (it does in the container). Would you recommend that I use volumes to expose this socket on my host? Or is there better way to runwal-e
on a docker host on a PG instance that's running inside of a container?I have no trouble connecting with:
The text was updated successfully, but these errors were encountered: