Jump to content

  • Docker Tab IP view broken on --network bridged containers

    alturismo

    By alturismo

      • Minor

    as this is open since many releases, just more or less as reminder

     

    when using the --net=container function ...

     

    expected behaviour

    either keep the IP / Ports field blank (as before)

    or insert the same entries from the "Host Docker" --net=conatiner:<DOCKERNAME>

     

    currently its 1st blank (expected), but after some dockers is updating ... it will take the entrys from the latest installed/updated docker

     

    sample here, oscam is --net=network:hideme_privoxy

    image.thumb.png.f5793c06f71affb839dfe7b1ac45477d.png

     

    but the shown IP/Port mapping is from a total different docker, as you see here from homeassistant (upper hideme_...)

     

    both containers received a update and this happens then ...

     

    this is only cosmetic, but can lead to wrong conclusions for some users ... and is open since a while aready ;)

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    There are no comments to display.



    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.

×
×
  • Create New...