Improve setup guide for AdguardHome running in Docker

tobiade commented 1 month ago

Prerequisites

[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to request a feature or enhancement and not ask a question

The problem

Hello! After successfully setting up AdGuardHome via the Docker installation on a Raspberry Pi, the setup guide states that the DNS server is available on these IP addresses:

The 172.17.0.2 IP address is the Docker virtual interface and is not exposed to other machines running on the same network as the Raspberry Pi.

Proposed solution

Clarify that the IP address for the Docker virtual interface should be used by clients on the same host
Specify the machine's IP address for use by external clients on the same network

If there's something I'm missing, please let me know. I'm also happy to make this change (if it's valid).

Alternatives considered and additional information

No response

kazantsev97 commented 1 month ago

how do I hide the ports from everyone and leave them only locally?

ric-m commented 1 month ago

Agreed. All my containers use a unified common network. All my containers are set to use fixed IPs within a reserved range of the router's DHCP configuration. Yet I'm struggling to find any rationale for defaulting to 127.0.0.1. Ric

jmrplens commented 1 month ago

In my case I use the IP 172.17.0.2 for the clients of my LAN 192.168.0.0/24; 192.168.99.0/24; 192.168.100.0/24; 192.168.200.0/24. I keep it isolated on the 172.17.0.0.0 network.

I do not use the one of the host (192.168.0.X). Whether or not you can access that IP from the outside depends on the routing you do on your router or switch. You can indicate that to access the internal IP you have to route, and that from the host you have to configure the host firewall to accept ex. 53/UDP, 443/TCP, 853/UDP (if it exists. I hope so!) and it can be used as DNS server.

AdguardTeam / AdGuardHome