June 17, 20233 yr Good morning, I have found previous comments about Docker port mapping issues. Attempted to install 'ChangeDetection' from two different repos. My base port of 5000, is already in use, and Docker App warned me. It offered -p to change and remap, and I did so (5000-->6000). It is set as Bridge mode. It didn't load. Logs show it's running (more proof it is in a moment) I then closed my existing 5000, remapped back to 5000, still won't open. Set the network to br0, defined an IP, and it'll open there. I have another low priority docker that I remapped from 3000-->4000 that DOES work. I then remapped again to 4500, it likewise works. Question is: Is this a Docker bug//issue, an app issue? I'll report it appropriately if we think it's whichever issue. I AM on 6.12RC8 Thanks!
June 18, 20233 yr 23 hours ago, bmpreston said: I AM on 6.12RC8 Why are you still on the RC when the stable for 6.12 is out?
June 18, 20233 yr Author 1 minute ago, JonathanM said: Why are you still on the RC when the stable for 6.12 is out? Only read about this this morning, literally upgrading now. I need to figure out how so many people know so much so quickly. lol I will test this again and see if the problem remains, but according to a different post, on the page for the docker app, I don't believe the docker app is accepting the input to change the port number upon request...
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.