Docker containers WebUI Port mapping bug?


Recommended Posts

Hi, im using nodered container that works on port: 1880 and i want to have a second instance of  the nodered so in apps settings i have enable the allow install of second instance.
i have then instaled a second instance and change de port to 1880 to 1889 that is not in use, but it always redirects me to the first instance port 1880,  and the port map shows correct 172.19.0.17:1889/TCP192.168.1.65:1889, i also tried change in WebUI the port in advanced mode and same it always send me to 1880
my question is if this is some type of bug or if there is another way to fix the problem ?

Link to comment
1 minute ago, Encarnacao said:

172.19.0.17:1889/TCP192.168.1.65:1889

That's wrong right there.  That shows you that you've changed both the internal port and the external port (you added another port mapping) to be 1889

 

It should show 172.19.0.17:1880/TCP192.168.1.65:1889 where the container still listens on 1880 internally, but everything else outside of it communicates on 1889.

 

The OS translates the WebUI entry (advanced view) and makes it what it should be.  IE: The webUI entry always refers to 1880

 

Alternatively, you're running the containers as a network type HOST (or BR0) in which case by definition any and all port mappings you set are ignored.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.