February 4, 20188 yr Could be a harmless error, since IPv6 is actually available now and some apps complain about not being able to bind to a port if there is an IPv6 binding. Is the webui for pihole accessible?
February 4, 20188 yr 5 hours ago, pinion said: I hear preclear is broken on 6.4.1 so I'm waiting Preclear is broken for any version 6.4 of unRAID. The recommendation is to uninstall preclear. It is not neccessary to use preclear anymore as in the V5 days. Nowadays clearing of drives is done in the background while the array stays operational and with notifications enabled you will receive instant warnings when a new disk has potential SMART issues. It is recommended to upgrade to 6.4.1. 5 hours ago, pinion said: I have br0, in the pihole docker I thought I could select br0 and then set the ip to something else Correct as long as you use a unique IP address for the docker container, it is free to use any port as required. Can you post a screenshot of the docker settings of pi-hole.
February 4, 20188 yr Just thought I'd report back, upgrading to 6.4.1, removing the IP from eth1 and configuring the docker network the container picks up the correct gateway and everything works flawlessly. Thanks for all the help!
February 5, 20188 yr On 2/4/2018 at 3:04 AM, bonienl said: Can you post a screenshot of the docker settings of pi-hole. Ok, I've upgraded to 6.4.1. Here is the screenshot. Thanks! Quote Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole' --net='bridge' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'ServerIP'='192.168.1.89' -e 'DNS1'='8.8.8.8' -e 'DNS2'='8.8.4.4' -e 'IPv6'='False' -e 'TZ'='America/New_York' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'DNSMASQ_LISTENING'='all' -p '53:53/tcp' -p '53:53/udp' -p '80:80/tcp' -v '/mnt/user/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/user/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN 'diginc/pi-hole:debian' b1bb4a1db516da072bfe5092af5bd7086ab01163dc427b24e12411669404fa02 /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint pihole (d881d154a3e4b46b924072ca2899eadbe54a5d81b0609368c9550cff66fb9253): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.The command failed.
February 5, 20188 yr You are doing it wrong. You need to delete all the port mappings, and keep INTERFACE on eth0. Then there is a drop-down above the port mappings, where the default is host or bridge. You'll need to change that to br0 or whatever docker network you want to use. I can't give you more detailed examples as I'm on mobile right now.
February 5, 20188 yr 12 minutes ago, ken-ji said: You are doing it wrong. You need to delete all the port mappings, and keep INTERFACE on eth0. Then there is a drop-down above the port mappings, where the default is host or bridge. You'll need to change that to br0 or whatever docker network you want to use. I can't give you more detailed examples as I'm on mobile right now. Thanks, in the drop down that used to only have "Host" and "Bridged" I now see None and br0. I selected br0 which gave me the option to enter 192.168.1.89. I didn't change anything else and the docker spun up once I hit apply. So all appears to be good. Thanks!
Archived
This topic is now archived and is closed to further replies.