Refactor: Reorganize services into standalone structure
This commit is contained in:
25
optimized/standalone/Pihole_Adguard/README.md
Normal file
25
optimized/standalone/Pihole_Adguard/README.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Pi-hole and AdGuard Home Chained DNS
|
||||
|
||||
This directory contains the `docker-compose.yml` for running a chained DNS setup with Pi-hole and AdGuard Home. Both services utilize `network_mode: host`, making this stack suitable for standalone deployment on a dedicated host.
|
||||
|
||||
## Running with Podman Compose
|
||||
|
||||
To run this stack using `podman-compose`:
|
||||
|
||||
1. Navigate to this directory:
|
||||
```bash
|
||||
cd optimized/standalone/Pihole_Adguard
|
||||
```
|
||||
2. Ensure you have replaced placeholder values like `WEBPASSWORD` with your actual secure password.
|
||||
3. Ensure the necessary host directories for volumes (`pihole_etc`, `pihole_dnsmasq`, `adguard_conf`, `adguard_work`, `adguard_certs`) exist or create them.
|
||||
4. Start the services:
|
||||
```bash
|
||||
podman-compose up -d
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
* This setup provides advanced DNS features, including ad-blocking (Pi-hole) and encrypted DNS (AdGuard Home).
|
||||
* `network_mode: host` is crucial for both services to integrate seamlessly with your host's network and act as primary DNS resolvers.
|
||||
* Careful configuration of upstream DNS in AdGuard Home (pointing to Pi-hole) is required post-installation.
|
||||
* Ensure the volume bind mounts are pointing to correct and persistent locations on your host.
|
||||
Reference in New Issue
Block a user