Docker pi-hole not blocking ads

Help docker
1

Finally got docker pi-hole to run on a Mac mini, but now it's hardly blocking any ads (< 1%). For context, I'm currently just setting my computer's (MacBook) WiFi DNS to the IP address of the machine running docker pi-hole.

I'm able to run nslookup pi.hole successfully:
image

But it looks like ads aren't being blocked from domains like flurry.com using the same nslookup tool:

image
image466×532 57.8 KB

Here's my debug token: https://tricorder.pi-hole.net/mnUj3rAc/

2

The debug log shows an issue with your adlist.
No domains were parsed and gravity count (the list of blocked domains) is zero.

gravity_count         0

To fix this, you need to update Gravity.

Using the web interface: go to Tools > Update Gravity and click on the "Update" button.
Using the command line: execute pihole -g

3

Gotcha, ok.

I tried both the web interface and the command line, and it appears that the gravity_count is still zero.

Here's a snippet of the console output when I use the web interface to update the gravity count:

image
image2012×1718 330 KB

Debug token: https://tricorder.pi-hole.net/XOkHhS37/

UPDATE: New debug token now that the old one has gone out of date: https://tricorder.pi-hole.net/swikkklI/

4

The contents shown (e.g. "# Title: StevenBlack/hosts") matches the actual contents of the file hosted at that URL.

It would seem that while the download of that blocklist succeeded, your Pi-hole container may not receive the correct file contents when reading it.
This may suggest that file system/permission issues may be involved.

Please share your docker-compose or docker run file.

5

Permission issues sound likely - I get a lot of messages like this in the container's logs:

2023-09-15 09:36:09 sed: couldn't open temporary file /etc/pihole/sedBpZgVk: Permission denied

Here's my docker-compose.yml file:

version: "3"

# Example taken from the README in pi-hole's github

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp"
    environment:
      TZ: 'America/Denver'
      WEBPASSWORD: '***'
      WEBTHEME: 'default-dark'
      FTLCONF_LOCAL_IPV4: 192.168.0.19
      DNSMASQ_LISTENING: all
    # Volumes store your data between container upgrades
    volumes:
      - './etc-pihole:/etc/pihole'
    restart: unless-stopped
9

Would you happen to know which filesystem ASUSTOR and/or Docker are applying, specifically for the volume mounts (./etc-pihole:/etc/pihole)?

Our development tells me that there may be an issue with certain filesystem types for sed, where sed may use an incorrect umask for temporary files.
Reportedly, this seems to be the case for fuse-overlayfs.

10

I don't know, and I'm not sure how I'd figure it out.

I fixed the problem though - the issue was that my docker-compose was lacking a top-level volumes attribute, so the volume was never fully created (i.e., docker volume ls didn't show any volumes, Docker Desktop didn't display any volumes, despite there being a local ./etc-pihole directory that docker created).

Here's my final docker-compose.yml that worked:

version: "3"

# Example taken from the README in pi-hole's github

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp"
    environment:
      TZ: 'America/Denver'
      WEBPASSWORD: '***'
      WEBTHEME: 'default-dark'
      FTLCONF_LOCAL_IPV4: 192.168.0.19
      DNSMASQ_LISTENING: all
    # Volumes store your data between container upgrades
    volumes:
      - 'etc-pihole:/etc/pihole'
    restart: unless-stopped

volumes:
  etc-pihole:

Thanks for your help!!