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: 

 

I second this.  This is clearly a bug as you can see from my attached screenshot.

 

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.