Docker pihole container: No webui, pihole not actually starting?

[mil1i]

Hello,

I attempted to run Pi-Hole today using docker on my Cent OS host. It seems to start, and in the log says [servicesd] done. HOWEVER, after that the docker log just shows "Starting lighttpd" repeating over and over again. The 'pihole -d' output suggests that dnsmasq, lighttpd, and pihole-FTL never start.

I cannot seem to access the webui however. I've tried accessing using the docker IP, host IP, hostname and the default http://pi.hole/admin.

I tried several different run options to see if it would change anything, but it did not make any difference.

Below I posted my last run options tested, and then some output from pihole -d.

Any assistance is greatly appreciated!

docker run -d
–name pihole
–dns 127.0.0.1
–dns 8.8.8.8
-e DNS1=“8.8.8.8”
-e DNS2=“8.8.4.4”
-e WEBPASSWORD=“pihole”
-p 53:53/tcp -p 53:53/udp -p 80:80
-e VIRTUAL_HOST="$hostname"
-v “/opt/pihole/var/run/lighttpd/:/var/run/lighttpd/”
-v “/opt/pihole/:/etc/pihole/”
-v “/opt/pihole/dnsmasq.d/:/etc/dnsmasq.d/”
-e ServerIP="$IP4"
-e ServerIPv6="$IP6"
–restart=always
diginc/pi-hole:debian

-rw-r--r--. 1 www-data www-data 29430 Jan 25 03:53 /var/log/lighttpd/error.log
   2018-01-25 03:52:05: (log.c.164) server started 
   2018-01-25 03:52:05: (mod_fastcgi.c.984) bind failed for: unix:/var/run/lighttpd/php.socket-0 No such file or directory 
   2018-01-25 03:52:05: (mod_fastcgi.c.1406) [ERROR]: spawning fcgi failed. 
   2018-01-25 03:52:05: (server.c.1022) Configuration of plugins failed. Going down. 
   2018-01-25 03:52:06: (log.c.164) server started 

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] pfinnovations.com is 10.0.0.10 via localhost (127.0.0.1)
[✗] Failed to resolve pfinnovations.com via Pi-hole (10.0.0.10)
[✓] doubleclick.com is 172.217.2.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] pichiincha.biz is fe80::3cc1:1b50:6aa3:b8c5 via localhost (::1)
[✗] Failed to resolve pichiincha.biz via Pi-hole (fe80::3cc1:1b50:6aa3:b8c5)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is 
[✗] lighttpd daemon is 
[✗] pihole-FTL daemon is

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] pfinnovations.com is 10.0.0.10 via localhost (127.0.0.1)
[✗] Failed to resolve pfinnovations.com via Pi-hole (10.0.0.10)
[✓] doubleclick.com is 172.217.2.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] pichiincha.biz is fe80::3cc1:1b50:6aa3:b8c5 via localhost (::1)
[✗] Failed to resolve pichiincha.biz via Pi-hole (fe80::3cc1:1b50:6aa3:b8c5)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is 
[✗] lighttpd daemon is 
[✗] pihole-FTL daemon is

[diginc]

did you add that volume mount of /var/run/lighttpd as a workaround to #217 ?

I think your host directory permissions on /opt/pihole/var/run/lighttpd/ still probably mismatch the lighttpd user inside the container. Try setting it's owner/group to id 33 per (chown 33.33 /opt/pihole/var/run/lighttpd/ )

$ docker exec pihole bash -c 'id www-data'
uid=33(www-data) gid=33(www-data) groups=33(www-data)

[mil1i]

Sorry I have been without internet the past 30+ hours. After reading this post you listed, that is odd!
Adding just: "-v /run" to my docker run command fixed it.

Thank you @diginc

[diginc]

I don't have a centos/fedora VM to test on at the moment but the new debian_dev tag may not need any /var volume mounts. More detail in #217

[mil1i]

@diginc I can try it out when I get home tonight. I tried again with the debian tag thinking that was what you posted, whoops! I will try tonight with the debian_dev tag.