I'm planning to run AdGuard Home in a Docker container on a UGREEN DXP480T Plus NAS. If you've set this up, I'd appreciate any practical tips, configuration advice, or feedback about things to watch out for—especially networking and making sure individual client devices appear correctly.
3 Answers
Host networking is another straightforward option. A basic Compose setup can look like this:
services:
adguardhome:
image: adguard/adguardhome
container_name: Adguard_Home
network_mode: host
volumes:
- /volume1/docker/adguardhome/conf:/opt/adguardhome/conf
- /volume1/docker/adguardhome/work:/opt/adguardhome/work
restart: always
Persisting the configuration and working directories is important so updates or restarts don’t erase your settings. Depending on your network setup, you may need to adjust the configuration so AdGuard Home sees each device’s individual IP instead of treating all DNS requests as coming from one address.
A lot of NAS users run AdGuard Home this way without major problems. The main things to plan for are giving it a stable IP, avoiding port conflicts with the NAS management interface, and making sure your router uses the AdGuard Home address as its DNS server. Test the setup with a few devices before changing the DNS settings for the entire network.
Yes, it works well on a NAS. Docker Compose is a good way to manage it, and using a macvlan network can make assigning AdGuard Home its own IP address easier. Just be careful when following AI-generated troubleshooting advice and verify the settings before applying them.
That was the main adjustment I needed too. The initial setup worked, but the client list only showed a single IP until I changed the networking configuration.