This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/superset.git
The following commit(s) were added to refs/heads/master by this push:
new 546cc18475 docs: update installing-superset-using-docker-compose.mdx
(#20958)
546cc18475 is described below
commit 546cc18475024d91016c82aa62a53b507d1b3520
Author: Alexander Likhachev <[email protected]>
AuthorDate: Wed Sep 28 03:01:20 2022 +0300
docs: update installing-superset-using-docker-compose.mdx (#20958)
---
docs/docs/installation/installing-superset-using-docker-compose.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/docs/docs/installation/installing-superset-using-docker-compose.mdx
b/docs/docs/installation/installing-superset-using-docker-compose.mdx
index 89ed9f1d63..7be1156f16 100644
--- a/docs/docs/installation/installing-superset-using-docker-compose.mdx
+++ b/docs/docs/installation/installing-superset-using-docker-compose.mdx
@@ -116,4 +116,4 @@ When running Superset using `docker` or `docker-compose` it
runs in its own dock
Here the instructions are for connecting to postgresql (which is running on
your host machine) from Superset (which is running in its docker container).
Other databases may have slightly different configurations but gist would be
same and boils down to 2 steps -
1. **(Mac users may skip this step)** Configuring the local
postgresql/database instance to accept public incoming connections. By default
postgresql only allows incoming connections from `localhost` only, but
re-iterating once again, `localhosts` are different for host machine and docker
container. For postgresql this involves make one-line changes to the files
`postgresql.conf` and `pg_hba.conf`, you can find helpful links tailored to
your OS / PG version on the web easily for this tas [...]
-2. Instead of `localhost`, try using `host.docker.internal` (Mac users) or
`172.18.0.1` (Linux users) as the host name when attempting to connect to the
database. This is docker internal detail, what is happening is that in Mac
systems docker creates a dns entry for the host name `host.docker.internal`
which resolves to the correct address for the host machine, whereas in linux
this is not the case (at least by default). If neither of these 2 hostnames
work then you may want to find the [...]
+2. Instead of `localhost`, try using `host.docker.internal` (Mac users,
Ubuntu) or `172.18.0.1` (Linux users) as the host name when attempting to
connect to the database. This is docker internal detail, what is happening is
that in Mac systems docker creates a dns entry for the host name
`host.docker.internal` which resolves to the correct address for the host
machine, whereas in linux this is not the case (at least by default). If
neither of these 2 hostnames work then you may want to f [...]