System changes when using -NET_ADMIN flag

Expected Behaviour:

Hardware: Raspberry Pi 4B
OS: Raspian
Type of Installation: Docker container using official Docker-compose file (Web interface mapped to port 8112 instead of 80 and Time zone changed to Berlin)
Router: Unitymedia Connect Box (Shitty router provided by ISP)
Connection to router: Cat7 Patch cable (Tried different Ports and cables)

  • After Installation i expected pihole to work as advertised and my Network to not crash and burn.
  • I do not expect the Pihole to show any network activity as long as nothing is configured to use it as a DNS

Actual Behaviour:

  • The Pi does not get a IPv4 adress thorugh the router anymore, only IPv6
  • The Router crashes whenever there is some more intense activity on the network regarding the Pi (Saving files to nextcloud, streaming music via navidrome...)
  • Problems presist after "removing" the installation with docker-compose down

Now I know that no amount of missconfiguration should lead to a router-crash. This is obviously the fault of my shitty ISPs router. But I know that pihole did something to my Network as things were fine before. I suspect, that the Pi tries to use Pihole as a DHCP server and there is some kind of loop but then again I am just a script kiddy that wanted a pihole and knows nothing about DHCP

It would be helpfull to know which configuration of the host system is changed when using the -NET_Admin flag

There was a different thread about a similar problem but the thread was somewhat convoluted and did not resolve the issue so it did not bring me closer to the goal

Any help is greatly apreciated. I know this is a dumpster fire and I am sorry for existing. But i am out of ideas unfortunately

Debug Token:

I reinstalled to get a debug log. It would not upload (Whyever, likely because i was stuck on IPV6 again) It is attached below

This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations.  This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected.  Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2022-02-17:19:44:49 debug log has been initialized.
[i] System has been running for 0 days, 13 hours, 40 minutes

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v5.8.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/pi-hole.git (fetch)
             origin	https://github.com/pi-hole/pi-hole.git (push)
[i] Branch: master
[i] Commit: v5.8.1-0-g875ad04

*** [ DIAGNOSING ]: Web version
[i] Web: v5.10.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.10.1-0-gcb7a866

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v5.13 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.53

*** [ DIAGNOSING ]: php version
[i] 7.3.31

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  10
[i] dig response:  dig: couldn't get address for 'ns1.pi-hole.net': failure
[✗] Distro:  Debian
[✗] Error: Debian is not a supported distro (https://docs.pi-hole.net/main/prerequisites/)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: FirewallD
[✓] Firewalld service not detected

*** [ DIAGNOSING ]: Processor
[✓] armv7l

*** [ DIAGNOSING ]: Disk usage
   Filesystem      Size  Used Avail Use% Mounted on
   overlay          59G   11G   46G  19% /
   tmpfs            64M     0   64M   0% /dev
   tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
   /dev/root        59G   11G   46G  19% /etc/pihole
   shm              64M  1.1M   63M   2% /dev/shm
   tmpfs           1.9G     0  1.9G   0% /proc/asound
   tmpfs           1.9G     0  1.9G   0% /sys/firmware

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    172.19.0.2/16

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 172.19.0.1
   * Pinging 172.19.0.1...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  on lo (127.0.0.1)
[✓] No IPv4 address available on eth0@if16
[✗] Failed to resolve doubleclick.com 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
[✓] No IPv6 address available on lo
[✓] No IPv6 address available on eth0@if16
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 0

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

*** [ DIAGNOSING ]: Pi-hole-FTL full status
[i] systemctl:  command not found

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    PIHOLE_INTERFACE=eth0
    QUERY_LOGGING=true
    BLOCKING_ENABLED=true

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Thu, 17 Feb 2022 19:45:15 GMT
Cache-Control: max-age=0
Date: Thu, 17 Feb 2022 19:45:15 GMT
Server: lighttpd/1.4.53

[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity Database
-rw-rw-r-- 1 pihole pihole 92K Feb 16 19:55 /etc/pihole/gravity.db

*** [ DIAGNOSING ]: Info table
   property              value                                   
   --------------------  ----------------------------------------
   version               15                                      
   Last gravity run finished at: 

   ----- First 10 Gravity Domains -----


*** [ DIAGNOSING ]: Groups
   id    enabled  name                                                date_added           date_modified        description                                       
   ----  -------  --------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   0           1  Default                                             2022-02-16 19:55:54  2022-02-16 19:55:54  The default group                                 

*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)

*** [ DIAGNOSING ]: Clients

*** [ DIAGNOSING ]: Adlists
   id     enabled  group_ids     address                                                                                               date_added           date_modified        comment                                           
   -----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   1            1  0             https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts                                      2022-02-16 19:55:54  2022-02-16 19:55:54  Migrated from /etc/pihole/adlists.list            

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 0 Feb 16 19:55 /etc/pihole/custom.list

-rw-r--r-- 1 pihole pihole 132 Feb 17 06:05 /etc/pihole/pihole-FTL.conf
   REPLY_ADDR4=0.0.0.0

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1.4K Feb 17 06:05 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/local.list
   addn-hosts=/etc/pihole/custom.list
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   log-async
   server=8.8.8.8
   server=8.8.4.4
   interface=eth0

-rw-r--r-- 1 root root 2.2K Feb 16 20:53 /etc/dnsmasq.d/06-rfc6761.conf
   server=/test/
   server=/localhost/
   server=/invalid/
   server=/bind/
   server=/onion/

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 0 Feb 16 20:53 /etc/lighttpd/external.conf

-rw-r--r-- 1 root root 3.7K Feb 16 20:53 /etc/lighttpd/lighttpd.conf
   server.modules = (
       "mod_access",
       "mod_accesslog",
       "mod_auth",
       "mod_expire",
       "mod_redirect",
       "mod_setenv",
       "mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "/pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/run/lighttpd.pid"
   server.username             = "www-data"
   server.groupname            = "www-data"
   server.port                 = 80
   accesslog.filename          = "/var/log/lighttpd/access.log"
   accesslog.format            = "%{%s}t|%V|%r|%s|%b"
   index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
   url.access-deny             = ( "~", ".inc", ".md", ".yml", ".ini" )
   static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
   mimetype.assign = (
       ".ico"   => "image/x-icon",
       ".jpeg"  => "image/jpeg",
       ".jpg"   => "image/jpeg",
       ".png"   => "image/png",
       ".svg"   => "image/svg+xml",
       ".css"   => "text/css; charset=utf-8",
       ".html"  => "text/html; charset=utf-8",
       ".js"    => "text/javascript; charset=utf-8",
       ".json"  => "application/json; charset=utf-8",
       ".map"   => "application/json; charset=utf-8",
       ".txt"   => "text/plain; charset=utf-8",
       ".eot"   => "application/vnd.ms-fontobject",
       ".otf"   => "font/otf",
       ".ttc"   => "font/collection",
       ".ttf"   => "font/ttf",
       ".woff"  => "font/woff",
       ".woff2" => "font/woff2"
   )
   include_shell "cat external.conf 2>/dev/null"
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
   $HTTP["url"] =~ "^/admin/" {
       setenv.add-response-header = (
           "X-Pi-hole" => "The Pi-hole Web interface is working!",
           "X-Frame-Options" => "DENY"
       )
   }
   $HTTP["url"] =~ "^/admin/\.(.*)" {
       url.access-deny = ("")
   }
   $HTTP["url"] =~ "/(teleporter|api_token)\.php$" {
       $HTTP["referer"] =~ "/admin/settings\.php" {
           setenv.add-response-header = ( "X-Frame-Options" => "SAMEORIGIN" )
       }
   }
   expire.url = ( "" => "access plus 0 seconds" )

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1.8K Jan  5 23:09 /etc/cron.d/pihole
   21 4   * * 7   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   00 00   * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate --state /var/lib/logrotate/pihole /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local
   26 19  * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote
   @reboot root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 2.7K Feb 17 06:05 /var/log/lighttpd/error.log
   -----head of error.log------
   2022-02-16 20:55:53: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 20:56:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 230
   2022-02-16 20:56:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 231
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 58
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
   2022-02-16 20:57:48: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 20:57:48: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:27:03: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:27:03: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:36:36: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:36:36: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:38:30: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:38:30: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:49:43: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:49:43: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-17 07:05:16: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-17 07:05:16: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 

   -----tail of error.log------
   2022-02-16 20:55:53: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 20:56:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 230
   2022-02-16 20:56:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 231
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
   2022-02-16 20:56:51: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 58
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
   2022-02-16 20:57:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
   2022-02-16 20:57:48: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 20:57:48: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:27:03: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:27:03: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:36:36: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:36:36: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:38:30: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:38:30: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-16 21:49:43: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-16 21:49:43: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 
   2022-02-17 07:05:16: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-02-17 07:05:16: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 90K Feb 17 19:44 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2022-02-16 20:55:22.353 332M] Using log file /var/log/pihole-FTL.log
   [2022-02-16 20:55:22.353 332M] ########## FTL started on cdd6ab0ae37d! ##########
   [2022-02-16 20:55:22.353 332M] FTL branch: master
   [2022-02-16 20:55:22.353 332M] FTL version: v5.13
   [2022-02-16 20:55:22.353 332M] FTL commit: b197b69
   [2022-02-16 20:55:22.353 332M] FTL date: 2022-01-05 18:19:34 +0000
   [2022-02-16 20:55:22.353 332M] FTL user: pihole
   [2022-02-16 20:55:22.353 332M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
   [2022-02-16 20:55:22.354 332M] Creating mutex
   [2022-02-16 20:55:22.354 332M] Creating mutex
   [2022-02-16 20:55:22.355 332M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2022-02-16 20:55:22.355 332M]    SOCKET_LISTENING: only local
   [2022-02-16 20:55:22.356 332M]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2022-02-16 20:55:22.356 332M]    MAXDBDAYS: max age for stored queries is 365 days
   [2022-02-16 20:55:22.356 332M]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2022-02-16 20:55:22.356 332M]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2022-02-16 20:55:22.356 332M]    DBINTERVAL: saving to DB file every minute
   [2022-02-16 20:55:22.356 332M]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2022-02-16 20:55:22.356 332M]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2022-02-16 20:55:22.356 332M]    PRIVACYLEVEL: Set to 0
   [2022-02-16 20:55:22.356 332M]    IGNORE_LOCALHOST: Show queries from localhost
   [2022-02-16 20:55:22.356 332M]    BLOCKINGMODE: Null IPs for blocked domains
   [2022-02-16 20:55:22.356 332M]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2022-02-16 20:55:22.356 332M]    DBIMPORT: Importing history from database
   [2022-02-16 20:55:22.356 332M]    PIDFILE: Using /run/pihole-FTL.pid
   [2022-02-16 20:55:22.356 332M]    PORTFILE: Using /run/pihole-FTL.port
   [2022-02-16 20:55:22.357 332M]    SOCKETFILE: Using /run/pihole/FTL.sock
   [2022-02-16 20:55:22.357 332M]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2022-02-16 20:55:22.357 332M]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2022-02-16 20:55:22.357 332M]    GRAVITYDB: Using /etc/pihole/gravity.db
   [2022-02-16 20:55:22.357 332M]    PARSE_ARP_CACHE: Active
   [2022-02-16 20:55:22.357 332M]    CNAME_DEEP_INSPECT: Active
   [2022-02-16 20:55:22.357 332M]    DELAY_STARTUP: No delay requested.
   [2022-02-16 20:55:22.357 332M]    BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
   [2022-02-16 20:55:22.357 332M]    NICE: Cannot change niceness to -10 (permission denied)

   -----tail of pihole-FTL.log------
   [2022-02-17 07:05:16.746 411M]    CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
   [2022-02-17 07:05:16.746 411M]    CHECK_DISK: Warning if certain disk usage exceeds 90%
   [2022-02-17 07:05:16.746 411M] Finished config file parsing
   [2022-02-17 07:05:16.748 411M] Database version is 9
   [2022-02-17 07:05:16.748 411M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 1.1MB used, 67.1MB total, FTL uses 1.1MB)
   [2022-02-17 07:05:16.748 411M] Imported 0 alias-clients
   [2022-02-17 07:05:16.749 411M] Database successfully initialized
   [2022-02-17 07:05:16.798 411M] Imported 0 queries from the long-term database
   [2022-02-17 07:05:16.798 411M]  -> Total DNS queries: 0
   [2022-02-17 07:05:16.798 411M]  -> Cached DNS queries: 0
   [2022-02-17 07:05:16.798 411M]  -> Forwarded DNS queries: 0
   [2022-02-17 07:05:16.798 411M]  -> Blocked DNS queries: 0
   [2022-02-17 07:05:16.798 411M]  -> Unknown DNS queries: 0
   [2022-02-17 07:05:16.799 411M]  -> Unique domains: 0
   [2022-02-17 07:05:16.799 411M]  -> Unique clients: 0
   [2022-02-17 07:05:16.799 411M]  -> Known forward destinations: 0
   [2022-02-17 07:05:16.799 411M] Successfully accessed setupVars.conf
   [2022-02-17 07:05:16.800 411M] listening on 0.0.0.0 port 53
   [2022-02-17 07:05:16.800 411M] listening on :: port 53
   [2022-02-17 07:05:16.804 411M] PID of FTL process: 411
   [2022-02-17 07:05:16.805 411/T420] Listening on port 4711 for incoming IPv4 telnet connections
   [2022-02-17 07:05:16.805 411/T422] Listening on Unix socket
   [2022-02-17 07:05:16.805 411M] INFO: FTL is running as user pihole (UID 999)
   [2022-02-17 07:05:16.806 411M] Reloading DNS cache
   [2022-02-17 07:05:17.830 411/T423] gravityDB_count(SELECT value FROM info WHERE property = 'gravity_count';) - SQL error step no more rows available
   [2022-02-17 07:05:17.830 411/T423] Count of gravity domains not available. Please run pihole -g
   [2022-02-17 07:05:17.840 411/T423] Compiled 0 whitelist and 0 blacklist regex filters for 0 clients in 9.3 msec
   [2022-02-17 20:44:31.489 411M] Received: Real-time signal 0 (34 -> 0)
   [2022-02-17 20:44:31.662 411/T423] gravityDB_count(SELECT value FROM info WHERE property = 'gravity_count';) - SQL error step no more rows available
   [2022-02-17 20:44:31.663 411/T423] Count of gravity domains not available. Please run pihole -g
   [2022-02-17 20:44:31.666 411/T423] Compiled 0 whitelist and 0 blacklist regex filters for 0 clients in 2.8 msec
   [2022-02-17 20:44:33.101 411M] Received: Real-time signal 0 (34 -> 0)
   [2022-02-17 20:44:33.671 411/T423] gravityDB_count(SELECT value FROM info WHERE property = 'gravity_count';) - SQL error step no more rows available
   [2022-02-17 20:44:33.671 411/T423] Count of gravity domains not available. Please run pihole -g
   [2022-02-17 20:44:33.675 411/T423] Compiled 0 whitelist and 0 blacklist regex filters for 0 clients in 3.4 msec

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 668K Feb 17 06:05 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 240 Feb 17 06:05 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 4.0K Feb 17 06:05 /dev/shm/FTL-dns-cache
-rw------- 1 pihole pihole 4.0K Feb 17 06:05 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 56 Feb 17 06:05 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 12K Feb 17 06:05 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 4.0K Feb 17 06:05 /dev/shm/FTL-per-client-regex
-rw------- 1 pihole pihole 176K Feb 17 06:05 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Feb 17 06:05 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 80K Feb 17 06:05 /dev/shm/FTL-strings
-rw------- 1 pihole pihole 156K Feb 17 06:05 /dev/shm/FTL-upstreams

*** [ DIAGNOSING ]: contents of /etc

-rw-r--r-- 1 root root 37 Feb 17 06:05 /etc/dnsmasq.conf
   conf-dir=/etc/dnsmasq.d
   user=pihole

-rw-r--r-- 1 root root 38 Feb 16 20:53 /etc/resolv.conf
   nameserver 127.0.0.11
   options ndots:0

*** [ DIAGNOSING ]: Pi-hole diagnosis messages

*** [ DIAGNOSING ]: Locale
    LANG=

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 232K Feb 17 19:45 /var/log/pihole.log
   -----head of pihole.log------
   Feb 16 20:55:22 dnsmasq[334]: started, version pi-hole-2.87test4-18 cachesize 10000
   Feb 16 20:55:22 dnsmasq[334]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n IDN DHCP DHCPv6 Lua TFTP no-conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
   Feb 16 20:55:22 dnsmasq[334]: using nameserver 8.8.8.8#53
   Feb 16 20:55:22 dnsmasq[334]: using nameserver 8.8.4.4#53
   Feb 16 20:55:22 dnsmasq[334]: using only locally-known addresses for onion
   Feb 16 20:55:22 dnsmasq[334]: using only locally-known addresses for bind
   Feb 16 20:55:22 dnsmasq[334]: using only locally-known addresses for invalid
   Feb 16 20:55:22 dnsmasq[334]: using only locally-known addresses for localhost
   Feb 16 20:55:22 dnsmasq[334]: using only locally-known addresses for test
   Feb 16 20:55:53 dnsmasq[444]: started, version pi-hole-2.87test4-18 cachesize 10000
   Feb 16 20:55:53 dnsmasq[444]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n IDN DHCP DHCPv6 Lua TFTP no-conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
   Feb 16 20:55:53 dnsmasq[444]: using nameserver 8.8.8.8#53
   Feb 16 20:55:53 dnsmasq[444]: using nameserver 8.8.4.4#53
   Feb 16 20:55:53 dnsmasq[444]: using only locally-known addresses for onion
   Feb 16 20:55:53 dnsmasq[444]: using only locally-known addresses for bind
   Feb 16 20:55:53 dnsmasq[444]: using only locally-known addresses for invalid
   Feb 16 20:55:53 dnsmasq[444]: using only locally-known addresses for localhost
   Feb 16 20:55:53 dnsmasq[444]: using only locally-known addresses for test
   Feb 16 20:55:53 dnsmasq[444]: read /etc/hosts - 7 addresses
   Feb 16 20:55:53 dnsmasq[444]: read /etc/pihole/custom.list - 0 addresses

   -----tail of pihole.log------
   Feb 17 20:40:42 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:40:42 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:41:12 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:41:12 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:41:42 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:41:42 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:42:13 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:42:13 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:42:43 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:42:43 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:43:13 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:43:13 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:43:43 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:43:43 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:44:14 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:44:14 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:44:44 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:44:44 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0
   Feb 17 20:45:14 dnsmasq[411]: query[A] pi.hole from 127.0.0.1
   Feb 17 20:45:14 dnsmasq[411]: Pi-hole hostname pi.hole is 0.0.0.0


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole_debug.log

Can you post your docker-compose.yaml file?

Sure

version: "3"

# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp"
      - "8112:80/tcp"
    environment:
      TZ: 'Europe/Berlin'
      WEBPASSWORD: 'VerySecurePasswordIWillNotPost'
    # 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

It is identical to the docker-hub version appart from Timezone, TCP port and Password. Maybe i should mention that there are other docker networks but pihole is not part of them

That compose wouldn't enable Pi-hole's docker container to be a DHCP server. It looks like it's on the default bridge network and DHCP would need Host mode or some additional changes. Plus DHCP server is passive, it just responds to requests and you don't have any DHCP server pools declared.

I don't think Pi-hole is the culprit here, if the behavior is ongoing even after the container has stopped.

Adding the NET_ADMIN would just give that container ability to monitor the network it was attached to, which would be the docker default bridge.

Ok, thank you very much. In this case i am none the wiser but i must have managed to screw something up somewere else (even if i have no clue what)

Thanks for the Help and sorry for the faulty "bug report"

No problem, and about what NET_ADMIN does:

Interesting....

I can't help you but I can confirm that since I went back to the normal installation I haven't experienced this problem at all anymore. So it was definitely related to the docker/pihole setup I was using even though it was dismissed here.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.