I just installed the nginx-letsencrypt docker. It's working but I don't understand a quirk about it. It's set in bridge mode, it's drawing an ip from the dhcp(192.168.1.7); however, everything is binding to the unraid default ip of 192.168.1.6. The default landing page is pulling up on 192.168.1.6:5110 (the port I assigned, mostly just for now since 80 is taken on that ip by the unraid webui). Basically, why is it binding to the unraid box ip when it's in bridged mode and successfully drawing an ip from the dhcp?

The nginx-letsencrypt docker support thread which the author monitors would be a good place to ask this.

 

You can find the link by searching for nginx-letsencryprt in Community Applications.

 

Sent from my LG-H815 using Tapatalk

 

 

I just installed the nginx-letsencrypt docker. It's working but I don't understand a quirk about it. It's set in bridge mode, it's drawing an ip from the dhcp(192.168.1.7); however, everything is binding to the unraid default ip of 192.168.1.6. The default landing page is pulling up on 192.168.1.6:5110 (the port I assigned, mostly just for now since 80 is taken on that ip by the unraid webui). Basically, why is it binding to the unraid box ip when it's in bridged mode and successfully drawing an ip from the dhcp?

 

Bridge mode bridges ports, not ethernet. Docker containers don't get their own IPs from your router. They all run on the unraid server's IP. Bridged/mapped ports allow access to the containers.

 

How did you determine that it got an ip from the router's dhcp? It should only have an ip it gets from unraid, through a virtual ethernet bridge (172.17.X.X), which is not accessible outside of unraid

 

Perhaps I was mistaken and had a peripheral device on the network at the time I setup the docker. I just went ahead and re-read the host vs bridged explanation for dockers and I understand now what they meant. Thanks for clearing that up