Containers are ment to be used with docker networks making it a non-issue, most of the time you want your services to forward 80/443 since thats the default port your reverse proxy is going to call
Comment on Getting worn out with all these docker images and CLI hosted apps
falynns@lemmy.world 1 week ago
My biggest problem is every docker image thinks they’re a unique snowflake and how would anyone else be using such a unique port number like 80?
I know I can change, believe me I know I have to change it, but I wish guides would acknowledge it and emphasize choosing a unique port.
lilith267@lemmy.blahaj.zone 1 week ago
Auli@lemmy.ca 1 week ago
Why expose any ports at all. Just use reverse proxy and expose that port and all the others just happen internally.
lka1988@lemmy.dbzer0.com 1 week ago
Still gotta configure ports for the reverse proxy to access.
phoenixz@lemmy.ca 1 week ago
Reverse proxy still goes over a port
unit327@lemmy.zip 1 week ago
Most put it on port 80 with the perfectly valid assumption that the user is sticking a reverse proxy in front of it. Container should expose 80 not port forward 80.
PieMePlenty@lemmy.world 1 week ago
There are no valid assumptions for port 80 imo. Unless your software is literally a pure http server, you should assume something else has already bound to port 80.
Why do I have vague memories of Skype wanting to use port 80 for something and me having issues with that some 15 years ago?