you are viewing a single comment's thread
view the rest of the comments
[–] 31 points 9 months ago (6 children)

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.

  • source
  • hideshow 6 child comments
  • [–] 38 points 9 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 9 months ago* (last edited 9 months 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?
    Edit: I just realized this might be for containerized applications.. I'm still used to running it on bare metal. Still though.. 80 seems sacrilege.

  • source
  • parent
  • [–] 3 points 9 months ago (2 children)

    Why expose any ports at all. Just use reverse proxy and expose that port and all the others just happen internally.

  • source
  • parent
  • hideshow 2 child comments