Docker on RPi4 running AlmaLinux issue

General
1

I just attempted a deploy on RPi4 running AlmaLinux 8 with the following docker-compose file:

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"
      - "80:80/tcp"
    environment:
      TZ: 'America/New_York'
      PIHOLE_DNS_: 208.67.222.222;8.8.8.8
      
    # Volumes store your data between container upgrades
    volumes:
      - '/mnt/docker:/etc/pihole/'
      - '/mnt/docker:/etc/dnsmasq.d/'
    restart: unless-stopped

After deploy I am seeing this in the logs:

pihole  | Starting pihole-FTL (no-daemon) as pihole
pihole  | Stopping pihole-FTL
pihole  | pihole-FTL: no process found

I can log into the web interface but there is an error in the Pi-hole Diagnosis that states this:


2022-03-08 04:14:08	DNSMASQ_CONFIG	FTL failed to start due to bad option at line 1 of /etc/dnsmasq.d/GitHubVersions

Can someone tell what the issue may be?
Looking at the 'GitHubVersions' file I see this: v5.9 v5.11 v5.14

Just for awareness, I did have Pi-hole running at one time on RPi4 running AlmaLinux 8 but I wasn't using docker then, it was just a straight install of Pi-hole.
Thanks.

2

Don't use one mount for both directories. You're putting the files from /etc/pihole in to /etc/dnsmasq.d and anything in /etc/dnsmasq.d will be treated and read as a configuration file. Hence the GitHubVersions that really is in /etc/pihole showing as it existing in /etc/dnsmasq.d.

1 Like
3

Holy crap. Good catch. I can't believe I missed that. Thanks!
On my way to correct...

2 Likes
4

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