Jump to content
  • [6.12.4] 'Docker' Tab shows incorrect\unreadable information


    Jarik
    • Closed

    Is the 'Docker' page supposed to correctly display containers\stacks created by a Docker Compose file?  I've encountered several issues in this case. They appear as shown in the screenshot below:

     

    image.thumb.png.5f9288d61882cac505e260f8b8ab5880.png

    image.png.8393d990ba60854f9391ef9bd9fb83a7.png

     

    The required custom Docker networks were created using the code:

    docker network create revers-proxy
    docker network create homeassistant

     

    Below are some basic network settings that might be helpful:

    Settings -> Network Settings -> Enable bridging: No
    Settings -> Docker -> Preserve user defined networks: Yes
    Settings -> Docker -> Host access to custom networks: Enabled

     

    For my test, I created a simple 'docker-compose.yml' file:

    Spoiler
    services:
      nginx-proxy-manager:
        container_name: nginx-proxy-manager
        networks: 
          - revers-proxy
          - homeassistant
        ports:
          - '80:80'
          - '443:443'
          - '81:81'
        environment:
          - HOST_OS="Unraid"
          - HOST_HOSTNAME="Diskstation"
          - HOST_CONTAINERNAME="nginx-proxy-manager"
        labels:
          - net.unraid.docker.managed=dockerman
          - net.unraid.docker.icon=https://raw.githubusercontent.com/Jarikk/icons/main/unraid/nginx-proxy-manager.png
          - net.unraid.docker.webui=http://[IP]:[PORT:81]
        image: jc21/nginx-proxy-manager:2.10.4
    
      homeassistant:
        container_name: homeassistant
        network_mode: host
        environment:
          - HOST_OS="Unraid"
          - HOST_HOSTNAME="Diskstation"
          - HOST_CONTAINERNAME="homeassistant"
        labels:
          - net.unraid.docker.managed=dockerman
          - net.unraid.docker.icon=https://raw.githubusercontent.com/Jarikk/icons/main/unraid/homeassistant.png
        image: lscr.io/linuxserver/homeassistant:2023.10.3
    
      homeassistant-zigbee2mqtt-bathroom:
        container_name: homeassistant-zigbee2mqtt-bathroom
        networks:
          - homeassistant
        environment:
          - HOST_OS="Unraid"
          - HOST_HOSTNAME="Diskstation"
          - HOST_CONTAINERNAME="homeassistant-zigbee2mqtt-bathroom"
        labels:
          - net.unraid.docker.managed=dockerman
          - net.unraid.docker.icon=https://raw.githubusercontent.com/Jarikk/icons/main/unraid/zigbee2mqtt.png
        image: koenkk/zigbee2mqtt:1.33.1
    
    networks:
      revers-proxy:
        external: true
      homeassistant:
        external: true

     

     

    I'd like to address the following issues visible in the screenshot above:

    1) Long network IDs are displayed instead of names.

    2) In case of the nginx-proxy-manager container, only a single network is displayed, even though the container is attached to two different networks in the Compose file.

    3) The nginx-proxy-manager container has several port mappings ('80:80', '443:443', '81:81') in the Compose file, but these mappings are not displayed in the corresponding column on the user interface.

    4) Incorrect port mappings are displayed for the zigbee2mqtt container. Although it has no mappings in the Compose file, the UI shows port mapping 8123, which is actually a port of the Home Assistant container attached to the HOST network.

    5) A minor user interface improvement can be made for long container names. For example, it would be better if the zigbee2mqtt container's name is positioned on the right next to the icon and not shifted down.

     

    Again, these issues are related to running containers using a Docker Compose file. When I tested this configuration by creating apps from the CA store, everything appeared to be correct:

     

    image.png.047e525d679805812d0daa5d32bc5a6f.png

     

     

     

    • Upvote 1



    User Feedback

    Recommended Comments

    Compose is a 3rd party plugin, not part of unraid so you should post in its support thread. And yeah integration isn't perfect outside of trivial stacks.

    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.

×
×
  • Create New...