If anything doesn’t work run the docker-compose without the -d option to the the console log.

Note: The -d option makes it run as a daemon. Now you can start you AdGuard Home docker with: docker-compose -f docker-compose.yaml up -d Get the AdGuard Docker image: docker image pull adguard/adguardhomeĬreate two config directories: /adguard/confĬreate a docker-compose.yaml file with the following content: version: '3' You can use anything here or even just call it “fd00::” which is the default but not recommended as it might interfere with other networks. The “fd59:c039:d3b8:d3b8” is a random prefix that is used for the IPv6 subnet. The parent is “eth0” which is the physical interface and you might to change this to whatever your physical interface is. This will create a virtual LAN called “local_lan”. To avoid all this problem I am creating a own docker network using the macvlan driver so the host is visible as a host on the local network. Especially on Ubuntu port 53 is per default used by the DNS Stubresolver and in order to get AdGuard Home working this needs to be disabled. For AdGuardHome this is sometimes not desired as it uses default ports, like port 53, that might already be used by the host system. The simplest way to run a docker container is to use the host network.

On a Debian based system docker compose can be installed with: sudo apt install docker-compose If you want to use IPv6 networking make sure you do this after the installation: Īlso I am using docker compose to make it easier to manage the containers. Details about installing Docker can be found here: Docker installįor the purpose of this blog I am not going into details of installing Docker itself and assume a system with docker installed exists. This blog will explain how to install AdGuard Home in a Docker container and enable IPv6 networking in order to enable IPv6 DNS resolution.

Adguard home synology