Logs are stored in the Docker image, causing it to grow

[spants]

Logs are being written to /var/logs causing the docker to expand over time

This is a...

• [ x] Issue trying to run the docker image

Description

Logs for pihole are being written to /var/logs rather than a volume

Expected Behavior

request that they are written to an external volume

Actual Behavior

fills up /var/log

Steps to Reproduce and debugging done

run docker and watch /var/logs

Your Environment

• Docker Host Operating System and OS Version: Unraid 6.5.2
• Docker Version:
• Hardware architecture: x86

[nxadm]

Edit the 01-pihole.conf and set it to write the log to a volume you mount in the container. Good catch.

/opt/docker/pihole/rw/dnsmasq.d# ack /var/log
01-pihole.conf
38:log-facility=/var/log/pihole.log

In my case, my volumes as like this:

# grep -A2 volumes: docker-compose.yml 
    volumes:
      - /opt/docker/pihole/rw/pihole:/etc/pihole
      - /opt/docker/pihole/rw/dnsmasq.d:/etc/dnsmasq.d

So, as an example, change log-facility=/var/log/pihole.log to log-facility=/etc/pihole/pihole.log.

[eku]

If you don't care, just use /dev/null as log output.

[a1lu]

This does not work for me. My 01-pihole.conf is overwritten on pihole start
from docke logs:

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

I am using latest docker image on raspi / libreELEC with the docker by Linuxserver.io.