36
Docker Container/Service with Same Port: Best Practices?
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jul 2023
36 points (95.0% liked)
Selfhosted
39677 readers
180 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
That wouldn't work if multiple containers use the same port (eg. 8000), right?
Without a docker network, I can just map
8001:8000and don't have that issue.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.
Okay, thanks! Maybe I'll try it in the future.
I've just posted a little example. I'd recommend doing it this way. No more thinking about what port is allready exposed etc