PI-Hole Docker restarting - Not accessible
Hello crew: I have followed instructions to install docker pi-hole instance. It starts, then goes into a restart status. Using Purple. The steps go flawlessly to install. I can do a restart docker, but after a few seconds, it shows restarting. My main network is 192.168.10.x/24 and in the docker-compose file, I configured the network for docker to 172.16.0.x/24. Do I need to put docker on the same network as my main? I don't think so. I am not too savvy on containers, so. this is a learning experience. See below. I shows as "starting", then "restarting". I can't access via web interface, of course. Thanks in advance for any assistance!
pi@Firewalla:~ (redacted) $ sudo systemctl restart docker
pi@Firewalla:~ (redacted $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b7c4ee4a450 pihole/pihole:v5.1.2 "/s6-init" 13 minutes ago Up 5 seconds (health: starting) 53/udp, 53/tcp, 80/tcp, 443/tcp, 67/udp pihole
pi@Firewalla:~ (redacted) $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b7c4ee4a450 pihole/pihole:v5.1.2 "/s6-init" 13 minutes ago Up 5 seconds (health: starting) 53/udp, 53/tcp, 80/tcp, 443/tcp, 67/udp pihole
pi@Firewalla:~ (redacted) $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b7c4ee4a450 pihole/pihole:v5.1.2 "/s6-init" 14 minutes ago Up 4 seconds (health: starting) 53/udp, 53/tcp, 80/tcp, 443/tcp, 67/udp pihole
pi@Firewalla:~ (redacted) $ sudo ip a show br-cdea7df26d5d
177: br-cdea7df26d5d: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:a0:96:7c:a7 brd ff:ff:ff:ff:ff:ff
inet 172.16.0.1/24 brd 172.16.0.255 scope global br-cdea7df26d5d
valid_lft forever preferred_lft forever
inet6 fe80::42:a0ff:fe96:7ca7/64 scope link
valid_lft forever preferred_lft forever
pi@Firewalla:~ (redacted) $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b7c4ee4a450 pihole/pihole:v5.1.2 "/s6-init" 27 minutes ago Restarting (1) 33 seconds ago pihole
-
One more note: here's my routing table. I am imagining that the 172.17.0.0/24 is normal? I did not configure that network. The docker bridge IP is "linkdown" and that other network that I did not create, is linkdown. I restart it and ping (at the very bottom), ICMP is failing to google's dns... so this container and associated network connections is not doing well...
pi@Firewalla:~ (redacted) $ ip route
default via [redacted] dev eth0 metric 1
1.1.1.1 via [redacted] dev eth0 metric 1
8.8.8.8 via [redacted] dev eth0 metric 1
[redacted] dev eth0 proto kernel scope link src [redacted]
172.16.0.0/24 dev br-cdea7df26d5d proto kernel scope link src 172.16.0.1 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.10.0/24 dev br0 proto kernel scope link src 192.168.10.1
192.168.12.0/24 dev br1 proto kernel scope link src 192.168.12.1
pi@Firewalla:~ (redacted) $ sudo docker run -it alpine ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
12 packets transmitted, 0 packets received, 100% packet loss
pi@Firewalla:~ (redacted) $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b7c4ee4a450 pihole/pihole:v5.1.2 "/s6-init" 45 minutes ago Restarting (1) 8 seconds ago pihole
-
FTL is failing and constantly restarting. Check the logs
sudo docker logs pihole
That being said I wouldn't run a docker pihole on a Purple. 2 issues - the firewalla itself does everything the pihole can do. So do it natively with the hardware.
Also the Purple barely has enough memory as is. Whatever the docker container is using is extremely limited. Even if you get it running you'll then have a poorly running docker and a poorly running purple.
Please sign in to leave a comment.
Comments
2 comments