61
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
61 points (96.9% liked)
Selfhosted
39251 readers
209 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:
- 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
Hi there,
thats an interesting question. I suppose it depends on what you need to do.
If you can, divert the ports in the run command or compose file with -p 4430:443 (run) Or Ports:
Then you tell the apps that need this port to use that one instead.
Thats the easiest solution I know of.
If you want a more elegant solution, you use custom domains with a reverse proxy like npm (nginx proxy manager).
You spin up npm and start defining hosts like cloud.yourhomedomain.com and define those over your dns if possible (router or in my case, pihole)
Docker is a universe of itself and you can invest hundreds of hours and still feel like a noob (good game mechanic btw, easy go get into, hard to master).
Hit me up if you need more info. Get familiar with stack overflow and the likes because you will need em. :)
Good luck
This is the correct answer.
I run several containers that offer up http/s and they obviously can't all use 80/443. Just adjust the left side of that port setting and you're good.
That plus a reverse proxy for offering these services up over the public internet, if you choose to do so, is a killer pair.
One addition to this: I actually run those in my private setup since I have highly sensitive data on there. Even if you’re not opening them, reverse proxy works wonders. :)