Internal DNS with Caddy and docker containers

At home, I run a number of docker containers on my Beelink S121. To easily access them with a memorable name, instead of http://192.168.1.2:823, I was running caddy-docker-proxy. It proxies docker containers with caddy through labels in a docker-compose.yml file. With it, I could access the service at https://my-service.lan. The basic usage is quite simple. First of all, we need caddy-docker-proxy running once (and that instance will be shared). A sufficient docker-compose.yml looks like this: yaml Copy services: caddy: image: caddy-docker-proxy ports: - 80:80 - 443:443 environment: - CADDY_INGRESS_NETWORKS=caddy networks: - caddy volumes: - /var/run/docker.sock:/var/run/docker.sock - caddy_data:/data restart: unless-stopped networks: caddy: external: true volumes: caddy_data: {} Then, to run f.e. adguard, I would use this docker-compose.yml: yaml Copy services: adguardhome: container_name: adguardhome image: adguard/adguardhome restart: unless-stopped volumes: -…