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.
|
||||
47
optimized/standalone/Pihole_Adguard/docker-compose.yml
Normal file
47
optimized/standalone/Pihole_Adguard/docker-compose.yml
Normal file
@@ -0,0 +1,47 @@
|
||||
# =============================================================================
|
||||
# DNS Chain: Router(:53) → AdGuard(:53,DOH,DOT) → Pi-hole(:5353) → Unbound(:5335)
|
||||
# =============================================================================
|
||||
# NOTE: For HAOS, use the run_command file instead - compose doesn't work there
|
||||
# NOTE: Post-install: Configure AdGuard upstream to <host-ip>:5053
|
||||
# NOTE: Pi-hole handles blocking/caching, AdGuard handles DOH/DOT encryption
|
||||
# =============================================================================
|
||||
|
||||
services:
|
||||
pihole:
|
||||
image: pihole/pihole:latest
|
||||
container_name: pihole
|
||||
network_mode: host
|
||||
environment:
|
||||
TZ: "America/Chicago"
|
||||
WEBPASSWORD: "YOURPASSWORD"
|
||||
FTLCONF_webserver_enabled: "true"
|
||||
FTLCONF_webserver_port: "7300"
|
||||
WEB_BIND_ADDR: "0.0.0.0"
|
||||
FTLCONF_dns_port: "5053"
|
||||
# DNS1/DNS2 are deprecated in Pi-hole v6+, use FTLCONF_dns_upstreams
|
||||
FTLCONF_dns_upstreams: "127.0.0.1#5335"
|
||||
volumes:
|
||||
- pihole_etc:/etc/pihole:rw
|
||||
- pihole_dnsmasq:/etc/dnsmasq.d:rw
|
||||
restart: unless-stopped
|
||||
|
||||
adguardhome:
|
||||
image: adguard/adguardhome:latest
|
||||
container_name: adguardhome
|
||||
network_mode: host
|
||||
environment:
|
||||
TZ: "America/Chicago"
|
||||
volumes:
|
||||
- adguard_conf:/opt/adguardhome/conf:rw
|
||||
- adguard_work:/opt/adguardhome/work:rw
|
||||
- adguard_certs:/opt/adguardhome/conf/certs:ro
|
||||
restart: unless-stopped
|
||||
depends_on:
|
||||
- pihole
|
||||
|
||||
volumes:
|
||||
pihole_etc:
|
||||
pihole_dnsmasq:
|
||||
adguard_conf:
|
||||
adguard_work:
|
||||
adguard_certs:
|
||||
Reference in New Issue
Block a user