this post was submitted on 23 Jul 2023
61 points (96.9% liked)

Selfhosted

40151 readers
547 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
61
Docker Container/Service with Same Port: Best Practices? (lemmy.dbzer0.com)
submitted 1 year ago by [email protected] to c/selfhosted
30 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 25 points 1 year ago (1 children)

That's the cool thing about docker you can just map a different external port.

https://docs.docker.com/network/

So if you look at the first flag it mentions: -p 8080:80

This means it's mapping external port 8080 to the internal port 80. You can change the 8080 to anything you want so you don't have conflicts.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

I have done what you mentioned and used a random port internally and kept 443 as the listening port. I am using Caddy to then direct the traffic reverse proxy it.

Thank you so much!

[–] [email protected] 6 points 1 year ago (1 children)

Just FYI, we may be using "internally" differently, but you can't change the port number to the right of the ":" That's usually a fixed port needed for the container (the internal docker port).

I think you are using "internal" to mean your local network port though, but in Dockers case it would be the "external port" (external to docker).

Flow would be: Proxy → External Docker Port (8080, can be variable) → Internal Docker Port (80, fixed per docker container)

Probably getting overly picky with wording, but wanted to make sure you knew that the inernal docker port can't be changed, just the mapping.

[–] [email protected] 2 points 1 year ago

Thanks for the heads-up on terminology! What you mentioned is how I set it up.

I had no idea that the ports could be configured like that! This is very helpful. Docker is a beast to get used to!