Unhealthy container after pihole upgrade

[billbazza]

I've been through every guide possible and can not get pihole to run in a healthy container.

Thing I have tried:

Remove and recreate container install older versions of pihole Remove Docker and install Docker-ce Disable IPv6

I don't know what else to do.

Please can someone direct me to the logs?

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 498a4a648f86 pihole/pihole:latest "/s6-init" 58 minutes ago Up 23 minutes (unhealthy) 0.0.0.0:53->53/udp, 0.0.0.0:53->53/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:67->67/udp pihole

Client: Docker Engine - Community Version: 20.10.2 API version: 1.41 Go version: go1.13.15 Git commit: 2291f61 Built: Mon Dec 28 16:18:13 2020 OS/Arch: linux/arm Context: default Experimental: true

Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:20 2022 OS/Arch: linux/arm Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.19.0 GitCommit: de40ad0

services: pihole: container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" - "443:443/tcp" environment: TZ: 'Europe/London' WEBPASSWORD: ##### # Volumes store your data between container upgrades volumes: - './etc-pihole/:/etc/pihole/' - './etc-dnsmasq.d/:/etc/dnsmasq.d/' # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN restart: unless-stopped

[billbazza]

Here is the container log:

Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Current Pi-hole version is v5.11.4 Current AdminLTE version is v5.13 Current FTL version is v5.16.1 Container tag is: 2022.07.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as pihole Starting crond Starting lighttpd [services.d] done. Stopping cron Stopping lighttpd Stopping pihole-FTL [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole

[i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [✓] Installed /etc/dnsmasq.d/01-pihole.conf [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf Existing DNS servers detected in setupVars.conf. Leaving them alone ::: Assigning password defined by Environment Variable [✓] New password set DNSMasq binding to default interface: eth0 Added ENV to php: "TZ" => "Europe/London", "PIHOLE_DOCKER_TAG" => "2022.07.1", "PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log", "ServerIP" => "0.0.0.0", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "0.0.0.0", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... [✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Current Pi-hole version is v5.11.4 Current AdminLTE version is v5.13 Current FTL version is v5.16.1 Container tag is: 2022.07.1 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting crond Starting lighttpd Starting pihole-FTL (no-daemon) as pihole [services.d] done.

[billbazza]

How I fixed it:

Edit docker-compose.yml and change the line image: pihole/pihole:latest to image: pihole/pihole:2022.02.1 Run docker-compose pull to download the old version (if you don't have it yet) Run docker-compose stop pihole to stop pihole Run docker-compose rm pihole to remove the previous image Run docker-compose up -d to start the pihole daemon again

[davemaul]

This is no fix but a workaround. :D

The solution here worked out for me: #1093

[PromoFaux]

Bullet 2 on this section of the README file : https://github.com/pi-hole/docker-pi-hole#upgrade-notes