• custom docker network does not allow entering container port in mapping

    aptalca

    By aptalca

      • Closed Minor

    Hi,

     

    We use custom networks (user defined bridge network) for docker containers for container to container direct connections with name resolution.

     

    One can manually create a user defined bridge network and it is available as an option under network in container settings. That part works great. 

     

    However, if that custom network is selected, when one tries to add a port mapping, there is no option for "container port", but only host port and other fields like name and description.

     

    To reproduce, pick any docker template (preferably one in host mode), switch it to the custom network and add a port mapping. You'll see that the container port option does not exist.

     

    To work around it, one has to select "bridge" first, add the port mappings, and then switch back to the custom network.

     

    Thanks

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    aptalca
    3 hours ago, bonienl said:

    This is not supported in the GUI. You'll need to make a feature request.

    I believe this is a bug.

     

    The feature was already requested and it was added. The "user defined bridge" networks are already listed in the gui as a network option.

     

    The bug is that when a user defined network is selected, the "add port" screen does not allow for entering in the "container port". See below screenshot.

     

    1717750076_Screenshot2018-10-15at15_37_38.thumb.png.0c05960198510c29acea9a7e2030a1c6.png

    Link to comment
    aptalca
    12 hours ago, ken-ji said:

    Seems like the UI doesn't fully support the custom bridge network yet. (Haven't had a use case for it myself)

    If you want your containers to be able to connect to each other using container names as hostnames, then the user defined bridge network works great. Letsencrypt takes advantage of this to standardize proxy configs by using container names instead of IPs

    Link to comment
    bonienl
    1 hour ago, aptalca said:

    I believe this is a bug.

    Nope. It was designed to treat all custom networks the same way. Adding custom bridge networks is an extension for which you can make a feature request.

    Edited by bonienl
    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
    Add a comment...

    ×   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.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.