JM2005 Posted July 6, 2014 Share Posted July 6, 2014 I have noticed a few docker containers that have the same internal port setting 8080. Good example is sabnzbd and headphones all have same port setting as 8080 on the container side. What can be done to correct this? *** Removed sickbeard as its on different port sorry *** Quote Link to comment
BRiT Posted July 6, 2014 Share Posted July 6, 2014 Shouldn't that be fine, as in that situation you just map a different host port into the container port? Quote Link to comment
itimpi Posted July 6, 2014 Share Posted July 6, 2014 I have noticed a few docker containers that have the same internal port setting 8080. Good example is sabnzbd and headphones all have same port setting as 8080 on the container side. What can be done to correct this? I do not see this as being an issue as the Docker RUN command can map any port internal to the container to a different port at the external level, thus avoiding collisions at the host level. The important point is that the instructions for each container document what ports have been used within the container. Quote Link to comment
JM2005 Posted July 6, 2014 Author Share Posted July 6, 2014 Well this is strange I had done that and it wouldn't work so I removed each one and redid them and they are working! Oh well don't know why it didn't work the first time. Sorry for the confusion. Thanks! Quote Link to comment
gfjardim Posted July 6, 2014 Share Posted July 6, 2014 I have noticed a few docker containers that have the same internal port setting 8080. Good example is sabnzbd and headphones all have same port setting as 8080 on the container side. What can be done to correct this? *** Removed sickbeard as its on different port sorry *** Well, for the savvy that's easy, but not if we want to make these dockers easy to use and deploy. Talk to the maintainer of the docker and see if he/she is willing to change it. I think we can track the ports already used, so new dockers could just avoid reusing them. Quote Link to comment
NAS Posted July 6, 2014 Share Posted July 6, 2014 No please dont do that. Having the container port the expected port and allowing the user to map it to a real port is docker best practice. More than that it is one of the conerstones of portability and scalability. If there is a user problem (which i agree there probably is) we should fix this is the user interface. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.