I am very new to using docker. I have been used to using dedicated VM’s and hosting the applications within the servers OS.

When hosting multiple applications/services that require the same port, is it best practice to spin up a whole new docker server or how should I go about the conflicts?

Ie. Hosting multiple web applications that utilize 443.

Thank you!

  • Scott@lem.free.asEnglish
    0·
    1 year ago

    Use a single reverse proxy on that one port… it can then route the requests to the various back ends.

    You probably want something that’s Docker-native like Traefik or Caddy.

    • EliteCow@lemmy.dbzer0.comOPEnglish
      0·
      1 year ago

      Thank you! I am using Caddy and was able to define a unique random port for the other containers and access this via reverse proxy!

      • herrfrutti@lemmy.worldEnglish
        0·
        1 year ago

        If the containers are all in the same network. You dont need to expose a port.

        Lets assume you create a docker network called reverse_proxy and add all your contaiers that you want to be accessed by the reverse proxy to that network (including caddy).

        Then you can address all containers through the hostname in you caddy file and the port would be the default configurated port from the container.

        So in the end you just expose the caddy container and nothing more.

        • d_k_bo@feddit.deEnglish
          0·
          1 year ago

          That wouldn’t work if multiple containers use the same port (eg. 8000), right?

          Without a docker network, I can just map 8001:8000 and don’t have that issue.

          • aguslr@lemmy.sdf.orgEnglish
            0·
            1 year ago

            Yes, it’d work just fine because each container listens on port 8000 of their own IP address, not the docker server’s IP address. Caddy/Traefik just redirects traffic to that port.