exposed port 80 and 443 about baseimage-docker HOT 9 CLOSED

It's because the web server listens on port 80 and 443 by default. Change it if you use different port numbers.

from baseimage-docker.

Is there any webserver in the baseimage ?
Aren't those ports only required to be exposed on the passenger-docker image ?

from baseimage-docker.

Oh, oops, I see what you mean now.

from baseimage-docker.

Actually, now that I've re-read the documentation, I think in baseimage-docker even port 22 should not be exposed. EXPOSE used to be used for exposing ports for port forwarding, but somewhere in 0.6 or 0.7 they changed it, and now EXPOSE is for exposing ports for use in linking. I will remove all EXPOSE entries.

from baseimage-docker.

I did not know that. Thank you for sharing 👍

from baseimage-docker.

Whats is the point of starting sshd in the container if the port to access it (22) is not exposed?

from baseimage-docker.

So that you can perform administration tasks.

Note that exposing the port is not required to be able to access the port. Exposing the port merely means that when you link the container to another container, that the port information is passed to that container. Whether a port is exposed or not, you can still access it through the container's private IP.

from baseimage-docker.

Indeed, it is accessible. Good to know, thanks.

It is not straight-forward to access a service when the port is not exposed, and it can be accessed only through the IP address of the container. So such access feels like a back door.

I am not saying it is wrong. It works, and if it is well documented then it is OK.

from baseimage-docker.

You are thinking about port forwarding. That is unrelated to exposing ports in the Dockerfile. As I mentioned before, exposing is only for use in linking containers. If you want to forward a port to the host then invoke 'docker run' with the right '-p' arguments.

from baseimage-docker.