With the coming of docker in NS7 I would share some thoughts with you about reverse proxy and docker, but firstly WHY ?
docker creates application running on a specific port, for instances portainer runs on the TCP 9000 but it is not a convenient way to recall it, either portainer.mydomain.com or mydomain.com/portainer could be a better way to retrieve the path.
therefore several manners could be used
- traefik or ngninx-proxy
It is a docker container, just run it and it will do the reverse proxy, domain based IIRC.
pro: it is easy for us, you even have a little UI
cons: we need to stop httpd running on 80 and 443 because it will be used by the proxy container.
- apache reverse proxy
we could do our reverse proxy with apache
pro : we could use both web application (installed manually or by rpm) and web container
cons : we have an UI and a backend to do
what need a reverse proxy for container
- force https
- restriction by IP access
well now i’m listening you