#Mapproxy postgres code#

There's nothing toД¬hange here unless you have code or users that insist thisДocumentation matches your environment. Know a port the image creator documented could be published but hasn'tД«een (since there's no host side of the map). It doesn't change howД¬ontainers communicate with each other. You can certainly expose more ports.ДЄdding comment to the answer which I believe is spot on since containers can communicate with each other in the same network irrespective of port exposed -Д®XPOSE is only documentation/metadata. In a nutshell, there is no way right now to unexpose the port 80 from parent Dockerfile. You can publish it on a specific host port as well.ДЎ023df9822e5 httpd:2.4 'httpd-foreground' 2 seconds ago Up 2 seconds 80/tcp, 0.0.0.0:8009->8009/tcp fervent_almeida See the 0.0.0.0:32768, it's now published to the host machine with a random ephemeral port i.e 32768. Argument -expose is equal to a statement using EXPOSEin Dockerfile.Дўc8c93a78e97 httpd:2.4 'httpd-foreground' 2 seconds ago Up 2 seconds 80/tcp, 0.0.0.0:32768->8009/tcp keen_swirles Output - CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESД628b537aded httpd:2.4 'httpd-foreground' 3 seconds ago Up 2 seconds 80/tcp, 8008/tcp objective_dewdney To allow this to happen you need to publish the ports. However, that's exposed only to the container network & will not allow communication via the defined ports to containers outside of the same network or to the host machine. Port 80 is exposed by the parent Dockerfile for httpd:2.4 image -ДЄ EXPOSE statement inside Dockerfile is going to give you an output eventually in docker ps. ProxyPass / retry=1 acquire=3000 timeout=20 Keepalive=On LoadModule alias_module modules/mod_alias.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule status_module modules/mod_status.so LoadModule unixd_module modules/mod_unixd.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_module modules/mod_proxy.so LoadModule version_module modules/mod_version.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule headers_module modules/mod_headers.so LoadModule log_config_module modules/mod_log_config.so LoadModule mime_module modules/mod_mime.so LoadModule filter_module modules/mod_filter.so LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule access_compat_module modules/mod_access_compat.so LoadModule authz_core_module modules/mod_authz_core.so

LoadModule authz_user_module modules/mod_authz_user.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so

LoadModule authn_core_module modules/mod_authn_core.so LoadModule authn_file_module modules/mod_authn_file.so LoadModule mpm_event_module modules/mod_mpm_event.so How can I find out when is exposing port 80, and crucially, how can I stop it from being exposed? Dockerfile FROM httpd:2.4Д®xec config ServerRoot '/usr/local/apache2' However, I don't believe this actually exposes the port anyway, and is intended more as a way of documenting which port should be exposed when running a container that utilizes the image. My Dockerfile contains only one EXPOSE declaration - EXPOSE 8080. When I shell on to the running container and search for instances of 'Listen 80', nothing shows up other than the instance of 'Listen 8080' that I added to nf. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESДў3c4e1f0ea66 my/apache:8080 '/docker-entrypoint.вЂ¦' 12 minutes ago Up 12 minutes 80/tcp, 0.0.0.0:8080->8080/tcp MyWebsite However, when I list my running containers using docker ps, I see that port 80 has also been exposed for some reason. When I build my image and run it, I'm able to successfully connect to my website via port 8080, so all seems well at this point. I have a Docker image that runs Apache, and I have configured Apache (through nf) to listen on port 8080.

Mapproxy postgres