Docker & AdGuard Home

I wanted a useful DNS-filtering service in my home lab and directed Hermes to deploy AdGuard Home, then checked the result from a client.

Hermes performed the agent-assisted Docker deployment under my direction, using the writable application workspace from the storage lab. Its report listed Compose configuration, configuration data, and working-data directories.

The deployment report described DNS bound to the private Tailscale network and administration through Tailscale Serve, with Funnel disabled. I am not publishing the private addresses or administration endpoint.

I validated the service from a Mac client. The report recorded normal name resolution and a blocked response for a test advertising domain, and I chose to leave the service running.

The report also recorded settings surviving a container restart. I distinguish that application check from a full host reboot, which was not demonstrated by this lab.

I directed an agent-assisted AdGuard Home deployment and validated client DNS filtering; the report records settings retained after a container restart.

The September 30 completion report and client confirmation support this result. Exact installation commands and the deployed Compose file were not retained in the detailed record.

The source's inspection commands and volume mapping are reconstructed examples, not recovered execution history. No host-reboot persistence test or network-wide blocking result is claimed.

I practiced directing and validating an assisted deployment instead of treating the agent's setup work as my own manual installation.

I learned to distinguish a running container, functional DNS filtering, and configuration retained after a container restart.