Jarik

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: 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: 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: