search

digtalaloha / synology-docker-pihole-unbound

20 stars 4 forks source link

routing error on deploy? #4

Open aalencia opened 10 months ago

aalencia commented 10 months ago

after i run docker compose:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-12-28T18:28:37-05:00" level=fatal msg="failed to add interface dockerda835d8 to sandbox: error setting interface "dockerda835d8" IP to 192.168.132.104/24: cannot program address 192.168.132.104/24 in sandbox interface because it conflicts with existing route {Ifindex: 112 Dst: 192.168.132.0/24 Src: 192.168.132.105 Gw: Flags: [] Table: 254}": unknown

I have my .env setup like this: HOSTNAME=Pi-hole PIHOLE_MACVLAN_IP=192.168.132.104 PIHOLE_BRIDGE_IP=192.168.132.105 UNBOUND_MACVLAN_IP=192.168.132.106 WEBPASSWORD='password' NETWORK_INTERFACE=eth0 MACVLAN_SUBNET=192.168.132.0/24 MACVLAN_GATEWAY=192.168.132.3 MACVLAN_IP_RANGE=192.168.132.104/30 BRIDGE_SUBNET=192.168.132.0/24 BRIDGE_GATEWAY=192.168.132.4 BRIDGE_IP_RANGE=192.168.132.4/32 TIMEZONE=America/New_York

Where my home isp router gateway is 192.168.0.1 and my wireless router gateway is 192.168.132.1

I'm sure this is just my misunderstanding of how macvlan is working.

aalencia commented 10 months ago

all the IP's in that config i made up based on my gateway being 192.168.132.1. My NAS that will host the pihole is 192.168.132.2.