muthubuntu commented on issue #15741:
URL: https://github.com/apache/superset/issues/15741#issuecomment-4579311527
One more potential solution - get the GATEWAY IP address from the postgresql
container you're trying to connect to:
`docker inspect container-running-pgsql`
Look at the bottom of the output for the Networks section:
```
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"DriverOpts": null,
"GwPriority": 0,
"NetworkID":
"149df16a0211a7d18ab4311643db23db55fd5780a5e62903bd892d92389d191c",
"EndpointID":
"b8fc1f0fff11ff4a4322808aa893d745e2de0cdef69b336b52231379aa516edf",
"Gateway": "172.17.0.1",
"IPAddress": "172.17.0.3",
"MacAddress": "6a:dc:01:9e:be:49",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"DNSNames": null
```
My "Gateway" value is 172.17.0.1, and when I use that for the HOST in the
Superset > Connect to Postgresql it connects quickly without issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
