- Minor
When publishing a docker container's ports from a bridge network, the syntax 192.168.2.10:8443 can be used instead of 8443 if you want the port published only by a specific IP address on the server. This works as expected. However, the Docker GUI will incorrectly list Unraid's IP address on the port mappings list, regardless of what IP address is actually use by the container.
The above in only a minor GUI reporting issue, everything works as expected despite the incorrect mapping information displayed. However, when trying to change Unraid's HTTPS WebUI port in Settings--Management Access, the UI prevents a port from being used that is also used by a Docker Container, even if that Container is using a different IP address and there would be no conflict. The command netstat -tulpn also shows the port in question is not in use on the main IP address. This issue only exists for HTTPS, the HTTP configuration allows it.
My example
Unraid's IP: 172.16.0.16
Secondary IP: 172.16.0.23
I have an Nginx container in a bridge network publishing port 443 to 172.16.0.23.
I would like to set Unraid's WebUI to 443, but it claims the port is already in use even though my use of a different IP address means no conflict exists.
As a workaround, I can do it in the other order, set Unraid to use port 443 and then configure Nginx to use 172.16.0.23:443, doing it that way works as expected. Each IP listens on port 443 with the expected service.