aptalca Posted March 4, 2019 Share Posted March 4, 2019 Currently, "user defined bridge networks" are recognized in docker container settings, but are treated incorrectly. They are treated similar to host/macvlan where the interface does not allow port mapping to different ports on the host (no container port option). They should be treated similar to the docker bridge network. Current workaround is to set the port mapping under the default docker bridge, and then switch to the user defined bridge network. Here's the previous bug report that was rejected: Quote Link to comment
IamSpartacus Posted April 17, 2019 Share Posted April 17, 2019 I second this. This is clearly a bug as you can see from my attached screenshot. Quote Link to comment
IamSpartacus Posted May 21, 2019 Share Posted May 21, 2019 Any acknowledgement on this? I'm not quite sure how this is not a bug but regardless this is something that should be at least "implemented" in the next minor release. 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.