explicitly bind pihole to only use 192.168.0.2, this fixes the clash with systemd-resolved, also removed linkes prometheus to see if we can fix the dns, this wasnt needed, but for now, as I dont really know what it does, Ive left it out until I dig more on that

This commit is contained in:
2020-10-18 12:52:34 +11:00
parent 228df68c48
commit bdd194f418

View File

@@ -342,12 +342,12 @@ services:
- '--web.console.libraries=/usr/share/prometheus/console_libraries'
- '--web.console.templates=/usr/share/prometheus/consoles'
- '--web.enable-lifecycle'
links:
- cadvisor:cadvisor
# links:
# - cadvisor:cadvisor
# - alertmanager:alertmanager
- node-exporter:node-exporter
depends_on:
- cadvisor
# - node-exporter:node-exporter
# depends_on:
# - cadvisor
restart: always
node-exporter:
@@ -433,8 +433,8 @@ services:
container_name: pihole
image: pihole/pihole:latest
ports:
- "53:53/tcp"
- "53:53/udp"
- "192.168.0.2:53:53/tcp"
- "192.168.0.2:53:53/udp"
environment:
TZ: 'Australia/Melbourne'
WEBPASSWORD: 'O701JH&%fDqIw836eTiw1LxzlGw!sn%c'