feat: add initial Portainer stack and template configurations for AdGuard Home
This commit is contained in:
0
templates/.gitkeep
Normal file
0
templates/.gitkeep
Normal file
20
templates/adguard/README.md
Normal file
20
templates/adguard/README.md
Normal file
@@ -0,0 +1,20 @@
|
||||
# AdGuard Home (Portainer template)
|
||||
|
||||
AdGuard Home is a network-wide software for blocking ads, trackers and unwanted content by acting as a DNS resolver with filtering capabilities. This template contains a ready-to-use configuration to deploy AdGuard Home as a Docker stack via Portainer.
|
||||
|
||||
Quick notes:
|
||||
|
||||
- Expose the DNS ports (`53/tcp` and `53/udp`) so your network devices can use AdGuard as a resolver.
|
||||
- Mount a persistent directory for configuration and DNS databases to preserve settings across container restarts.
|
||||
- Keep secrets (if any) out of this repository—use environment variables, Docker secrets, or Portainer credentials.
|
||||
|
||||
Usage:
|
||||
|
||||
1. Import the compose file or template into Portainer's Stacks/App Templates.
|
||||
2. Adjust the bind paths and ports to match your host and network.
|
||||
3. Deploy and point your devices or DHCP server to the AdGuard DNS address.
|
||||
|
||||
Helpful links:
|
||||
|
||||
- Official site: https://adguard.com/en/adguard-home/overview.html
|
||||
- Docs: https://github.com/AdguardTeam/AdGuardHome
|
||||
15
templates/adguard/docker-compose.yml
Normal file
15
templates/adguard/docker-compose.yml
Normal file
@@ -0,0 +1,15 @@
|
||||
services:
|
||||
adguard:
|
||||
image: adguard/adguardhome
|
||||
container_name: AdGuard
|
||||
mem_limit: 2g
|
||||
cpu_shares: 768
|
||||
security_opt:
|
||||
- no-new-privileges:true
|
||||
network_mode: host
|
||||
volumes:
|
||||
- /volume1/docker/adguard/config:/opt/adguardhome/conf:rw
|
||||
- /volume1/docker/adguard/data:/opt/adguardhome/work:rw
|
||||
environment:
|
||||
TZ: Europe/Dublin
|
||||
restart: always
|
||||
Reference in New Issue
Block a user