2026-10-04 16:49 UTC
Although I know it's not a Docker problem, in typical punter fashion, my punter mind is indoctrinated to BLAME Docker for this junk:
"This junk" currently being "every docker container wants to expose port 8080". When I have one that does this, it's OK, but it breaks the instant I put up a second container that exposes the same port. If I'm thinking, I can nip that in the bud by telling the compose to expose a different port.
Some install via a shell script. I want to do the compose myself.
Replies (0)
No replies.