@@ -104,7 +104,7 @@ of sudo to start Postfix, or if you wish to use an external mail server.
104104
105105*Default: <null> *
106106
107- If left un-set, the container will listen on port 80 for connections in plain
107+ If left un-set, the container will listen on port 5050 for connections in plain
108108text. If set to any value, the container will listen on port 443 for TLS
109109connections.
110110
@@ -122,7 +122,7 @@ for most users - in IPv4-only environments, this may need to be set to
122122
123123**PGADMIN_LISTEN_PORT **
124124
125- *Default: 80 or 443 (if TLS is enabled) *
125+ *Default: 5050 or 443 (if TLS is enabled) *
126126
127127Allows the port that the server listens on to be set to a specific value rather
128128than using the default.
@@ -227,14 +227,13 @@ instances.
227227
228228 sudo chown -R 5050:5050 < host_directory>
229229
230- On some filesystems that do not support extended attributes, it may not be
231- possible to run pgAdmin without specifying a value for *PGADMIN_LISTEN_PORT *
232- that is greater than 1024. In such cases, specify an alternate port when
233- launching the container by adding the environment variable, for example:
230+ The default listen port is 5050, which does not require any special
231+ privileges. If you need to use a different port, specify it when launching
232+ the container by adding the environment variable, for example:
234233
235234 .. code-block :: bash
236235
237- -e ' PGADMIN_LISTEN_PORT=5050 '
236+ -e ' PGADMIN_LISTEN_PORT=8080 '
238237
239238 Don't forget to adjust any host-container port mapping accordingly.
240239
@@ -280,22 +279,22 @@ certificate.
280279Examples
281280********
282281
283- Run a simple container over port 80 :
282+ Run a simple container over port 5050 :
284283
285284.. code-block :: bash
286285
287286 docker pull dpage/pgadmin4
288- docker run -p 80:80 \
287+ docker run -p 5050:5050 \
289288 -e ' PGADMIN_DEFAULT_EMAIL=user@domain.com' \
290289 -e ' PGADMIN_DEFAULT_PASSWORD=SuperSecret' \
291290 -d dpage/pgadmin4
292291
293- Run a simple container over port 80 , setting some configuration options:
292+ Run a simple container over port 5050 , setting some configuration options:
294293
295294.. code-block :: bash
296295
297296 docker pull dpage/pgadmin4
298- docker run -p 80:80 \
297+ docker run -p 5050:5050 \
299298 -e ' PGADMIN_DEFAULT_EMAIL=user@domain.com' \
300299 -e ' PGADMIN_DEFAULT_PASSWORD=SuperSecret' \
301300 -e ' PGADMIN_CONFIG_ENHANCED_COOKIE_PROTECTION=True' \
@@ -327,13 +326,13 @@ Sometimes it's desirable to have users connect to pgAdmin through a reverse
327326proxy rather than directly to the container it's running in. The following
328327examples show how this can be achieved. With traditional reverse proxy servers
329328such as `Nginx <https://www.nginx.com/ >`_, pgAdmin is running in a container on
330- the same host, with port 5050 on the host mapped to port 80 on the container,
329+ the same host, with port 5050 on the host mapped to port 5050 on the container,
331330for example:
332331
333332.. code-block :: bash
334333
335334 docker pull dpage/pgadmin4
336- docker run -p 5050:80 \
335+ docker run -p 5050:5050 \
337336 -e " PGADMIN_DEFAULT_EMAIL=user@domain.com" \
338337 -e " PGADMIN_DEFAULT_PASSWORD=SuperSecret" \
339338 -d dpage/pgadmin4
0 commit comments