Docker update to v5.7 causes FTL to crash at launch

Cilusse · February 16, 2021, 11:59pm

Confirmed fixed from some awesome contributors!

github.com/pi-hole/docker-pi-hole

PiHole on docker won't start anymore with the latest version

opened 09:25PM - 16 Feb 21 UTC

closed 11:56PM - 16 Feb 21 UTC

devedse

resolved

### Versions ``` Pi-hole version is v5.2.4 (Latest: v5.2.4) AdminLTE versi…on is v5.4 (Latest: v5.4) FTL version is v5.7 (Latest: v5.7) ``` My watchtower just automatically updated my PiHole running on a raspberry pi: ``` time="2021-02-16T20:41:57Z" level=info msg="Found new pihole/pihole:latest image (sha256:a2eef2ddff91c7117eacfcfb6927ea56d5dd51291c2282e66d1fca4d7b2ba5ce)" time="2021-02-16T20:42:40Z" level=info msg="Stopping /Pihole (3e1fae648dfb6d3bbadc5aa28017cfd77248012a5fa08191900662c07bfdb9ed) with SIGTERM" time="2021-02-16T20:42:46Z" level=info msg="Creating /Pihole" ``` However after the PiHole containers shows up as Unhealthy. Here's the container log: ``` [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] 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! [i] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf... [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf Converting DNS1 to PIHOLE_DNS_ Setting DNS servers based on PIHOLE_DNS_ variable ::: Pre existing WEBPASSWORD found DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "0.0.0.0", "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 https://mirror1.malwaredomains.com/files/justdomains ::: Testing pihole-FTL DNS: FTL started! ::: 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 [i] Neutrino emissions detected... [✓] Pulling blocklist source list into range [i] Preparing new gravity database... [✓] Preparing new gravity database [i] Using libz compression [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts [i] Status: Pending... [✓] Status: Retrieval successful [i] Received 60887 domains [i] Target: https://mirror1.malwaredomains.com/files/justdomains [i] Status: Pending... [✗] Status: Not found [✗] List download failed: using previously cached list [i] Received 26854 domains [i] Storing downloaded domains in new gravity database... [✓] Storing downloaded domains in new gravity database [i] Building tree... [✓] Building tree [i] Swapping databases... [✓] Swapping databases [i] Number of gravity domains: 87741 (87713 unique domains) [i] Number of exact blacklisted domains: 0 [i] Number of regex blacklist filters: 0 [i] Number of exact whitelisted domains: 1 [i] Number of regex whitelist filters: 0 [i] Cleaning up stray matter... [✓] Cleaning up stray matter [✓] DNS service is listening [✓] UDP (IPv4) [✓] TCP (IPv4) [✓] UDP (IPv6) [✓] TCP (IPv6) [✓] Pi-hole blocking is enabled Pi-hole version is v5.2.4 (Latest: v5.2.4) AdminLTE version is v5.4 (Latest: v5.4) FTL version is v5.7 (Latest: v5.7) [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as root Starting lighttpd Starting crond [services.d] done. Stopping pihole-FTL kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as root Stopping pihole-FTL kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as root Stopping pihole-FTL kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as root Stopping pihole-FTL kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as root Stopping pihole-FTL kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) as root Stopping pihole-FTL ``` ### Platform - OS and version: Linux dockerpi 5.4.83-v7+ - Platform: Raspberry PI ### Expected behavior PiHole should start correctly ### Actual behavior / bug PiHole FTL service won't start ### Steps to reproduce Steps to reproduce the behavior: 1. Update to the latest version ## Edit I've also checked the FTL log found by executing `cat /var/log/pihole-FTL.log` inside the docker container. This is the output: ``` [2021-02-16 22:31:06.202 7444M] ########## FTL started! ########## [2021-02-16 22:31:06.203 7444M] FTL branch: master [2021-02-16 22:31:06.209 7444M] FTL version: v5.7 [2021-02-16 22:31:06.210 7444M] FTL commit: 2999e2b5 [2021-02-16 22:31:06.210 7444M] FTL date: 2021-02-16 19:36:43 +0000 [2021-02-16 22:31:06.210 7444M] FTL user: root [2021-02-16 22:31:06.210 7444M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516 [2021-02-16 22:31:06.211 7444M] FATAL: create_shm(): Failed to create shared memory object "FTL-lock": File exists [2021-02-16 22:31:06.211 7444M] Initialization of shared memory failed. ```