Docker diff unexpectedly lists a large number of changes for pihole container

Question

Docker diff unexpectedly lists a large number of changes for pihole container

dlehammer opened this issue a year ago · 7 comments

This is a: Bug

Details

I was suprised that Docker diff for pihole lists a large number of changes (as the only container on my Docker host).

List the changed files and directories in a container᾿s filesystem since the container was created.

The expected output would be zero changes for a fully defined Docker image build ~ copying scripts etc. into the published image.
Besides what looks like state under /run, there's a also some .log files scattered about ~ logging should preferably adhere to the container logging convention.

Symptom discovered in 2023.11.0, still present in 2024.01.0.

$ sudo docker diff pihole
C /macvendor.db
C /opt
C /opt/pihole
C /opt/pihole/pihole-FTL-prestart.sh
C /opt/pihole/pihole-FTL-poststop.sh
C /run
A /run/pihole-FTL.pid
A /run/s6-linux-init-container-results
A /run/s6-linux-init-container-results/exitcode
A /run/s6-linux-init-container-results/haltcode
A /run/crond.pid
A /run/lighttpd.pid
A /run/s6
A /run/s6/basedir
A /run/s6/basedir/env
A /run/s6/basedir/env/PHP_ERROR_LOG
A /run/s6/basedir/env/S6_CMD_WAIT_FOR_SERVICES_MAXTIME
A /run/s6/basedir/env/S6_KEEP_ENV
A /run/s6/basedir/env/HOME
A /run/s6/basedir/env/HOSTNAME
A /run/s6/basedir/env/IPv6
A /run/s6/basedir/env/DNSMASQ_USER
A /run/s6/basedir/env/FTLCONF_LOCAL_IPV4
A /run/s6/basedir/env/PWD
A /run/s6/basedir/env/S6_BEHAVIOUR_IF_STAGE2_FAILS
A /run/s6/basedir/env/WEBPASSWORD
A /run/s6/basedir/env/phpver
A /run/s6/basedir/env/FTL_CMD
A /run/s6/basedir/env/PATH
A /run/s6/basedir/env/TZ
A /run/s6/basedir/env.orig
A /run/s6/basedir/run-image
A /run/s6/basedir/run-image/s6-linux-init-container-results
A /run/s6/basedir/run-image/s6-linux-init-container-results/exitcode
A /run/s6/basedir/run-image/service
A /run/s6/basedir/run-image/service/s6-linux-init-shutdownd
A /run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo
A /run/s6/basedir/run-image/service/s6-linux-init-shutdownd/run
A /run/s6/basedir/run-image/service/.s6-svscan
A /run/s6/basedir/run-image/service/.s6-svscan/SIGUSR1
A /run/s6/basedir/run-image/service/.s6-svscan/SIGUSR2
A /run/s6/basedir/run-image/service/.s6-svscan/SIGWINCH
A /run/s6/basedir/run-image/service/.s6-svscan/SIGTERM
A /run/s6/basedir/run-image/service/.s6-svscan/SIGPWR
A /run/s6/basedir/run-image/service/.s6-svscan/SIGQUIT
A /run/s6/basedir/run-image/service/.s6-svscan/crash
A /run/s6/basedir/run-image/service/.s6-svscan/finish
A /run/s6/basedir/run-image/service/.s6-svscan/SIGINT
A /run/s6/basedir/scripts
A /run/s6/basedir/scripts/rc.init
A /run/s6/basedir/scripts/rc.shutdown
A /run/s6/basedir/scripts/rc.shutdown.final
A /run/s6/basedir/bin
A /run/s6/basedir/bin/poweroff
A /run/s6/basedir/bin/reboot
A /run/s6/basedir/bin/shutdown
A /run/s6/basedir/bin/halt
A /run/s6/basedir/bin/init
A /run/s6/db
A /run/s6/db/db
A /run/s6/db/lock
A /run/s6/db/n
A /run/s6/db/resolve.cdb
A /run/s6/db/servicedirs
A /run/s6/db/servicedirs/cron
A /run/s6/db/servicedirs/cron/finish
A /run/s6/db/servicedirs/cron/run
A /run/s6/db/servicedirs/lighttpd
A /run/s6/db/servicedirs/lighttpd/finish
A /run/s6/db/servicedirs/lighttpd/run
A /run/s6/db/servicedirs/lighttpd-access-log
A /run/s6/db/servicedirs/lighttpd-access-log/finish
A /run/s6/db/servicedirs/lighttpd-access-log/run
A /run/s6/db/servicedirs/lighttpd-error-log
A /run/s6/db/servicedirs/lighttpd-error-log/run
A /run/s6/db/servicedirs/lighttpd-error-log/finish
A /run/s6/db/servicedirs/pihole-FTL
A /run/s6/db/servicedirs/pihole-FTL/finish
A /run/s6/db/servicedirs/pihole-FTL/run
A /run/s6/db/servicedirs/s6rc-fdholder
A /run/s6/db/servicedirs/s6rc-fdholder/data
A /run/s6/db/servicedirs/s6rc-fdholder/data/autofilled
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/gid
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/gid/0
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/gid/0/allow
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/gid/0/env
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/allow
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_RETRIEVE_REGEX
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_SETDUMP
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_STORE_REGEX
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_GETDUMP
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_LIST
A /run/s6/db/servicedirs/s6rc-fdholder/data/rules/uid/self
A /run/s6/db/servicedirs/s6rc-fdholder/notification-fd
A /run/s6/db/servicedirs/s6rc-fdholder/run
A /run/s6/db/servicedirs/s6rc-oneshot-runner
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/gid
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/gid/0
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/gid/0/allow
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/uid
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/uid/self
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/uid/0
A /run/s6/db/servicedirs/s6rc-oneshot-runner/data/rules/uid/0/allow
A /run/s6/db/servicedirs/s6rc-oneshot-runner/notification-fd
A /run/s6/db/servicedirs/s6rc-oneshot-runner/run
A /run/s6/legacy-services
A /run/s6/workdir
A /run/s6-rc
A /run/s6-rc:s6-rc-init:EMHMEP
A /run/s6-rc:s6-rc-init:EMHMEP/state
A /run/s6-rc:s6-rc-init:EMHMEP/compiled
A /run/s6-rc:s6-rc-init:EMHMEP/lock
A /run/s6-rc:s6-rc-init:EMHMEP/prefix
A /run/s6-rc:s6-rc-init:EMHMEP/scandir
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/finish
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/pihole-FTL/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/autofilled
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/gid
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/gid/0
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/gid/0/allow
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/gid/0/env
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/self
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/allow
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_GETDUMP
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_LIST
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_RETRIEVE_REGEX
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_SETDUMP
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/data/rules/uid/0/env/S6_FDHOLDER_STORE_REGEX
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/down
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/notification-fd
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-fdholder/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/uid
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/uid/0
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/uid/0/allow
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/uid/self
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/gid
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/gid/0
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/data/rules/gid/0/allow
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/notification-fd
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/s
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/s.lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/s6rc-oneshot-runner/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/finish
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/cron/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/finish
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/finish
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/supervise/lock
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/down
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-access-log/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/down
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/event
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/finish
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/run
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/supervise
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/supervise/status
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/supervise/control
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/supervise/death_tally
A /run/s6-rc:s6-rc-init:EMHMEP/servicedirs/lighttpd-error-log/supervise/lock
C /run/lighttpd
A /run/lighttpd/pihole-php-fastcgi.socket-0
C /run/pihole
A /run/pihole/FTL.sock
A /run/service
A /run/service/.s6-svscan
A /run/service/.s6-svscan/SIGWINCH
A /run/service/.s6-svscan/control
A /run/service/.s6-svscan/crash
A /run/service/.s6-svscan/finish
A /run/service/.s6-svscan/SIGUSR2
A /run/service/.s6-svscan/lock
A /run/service/.s6-svscan/SIGINT
A /run/service/.s6-svscan/SIGPWR
A /run/service/.s6-svscan/SIGQUIT
A /run/service/.s6-svscan/SIGTERM
A /run/service/.s6-svscan/SIGUSR1
A /run/service/lighttpd
A /run/service/lighttpd-error-log
A /run/service/s6-linux-init-shutdownd
A /run/service/s6-linux-init-shutdownd/event
A /run/service/s6-linux-init-shutdownd/fifo
A /run/service/s6-linux-init-shutdownd/run
A /run/service/s6-linux-init-shutdownd/supervise
A /run/service/s6-linux-init-shutdownd/supervise/death_tally
A /run/service/s6-linux-init-shutdownd/supervise/lock
A /run/service/s6-linux-init-shutdownd/supervise/status
A /run/service/s6-linux-init-shutdownd/supervise/control
A /run/service/cron
A /run/service/lighttpd-access-log
A /run/service/pihole-FTL
A /run/service/s6rc-fdholder
A /run/service/s6rc-oneshot-runner
A /run/crond.reboot
C /var
C /var/lib
C /var/lib/apt
A /var/lib/apt/daily_lock
C /var/lib/logrotate
A /var/lib/logrotate/pihole
A /var/lib/logrotate/status
C /var/backups
A /var/backups/alternatives.tar.0
A /var/backups/apt.extended_states.0
A /var/backups/dpkg.arch.0
A /var/backups/dpkg.diversions.0
A /var/backups/dpkg.statoverride.0
A /var/backups/dpkg.status.0
C /var/log
A /var/log/alternatives.log.1
C /var/log/apt
C /var/log/apt/history.log
A /var/log/apt/history.log.1.gz
C /var/log/apt/term.log
A /var/log/apt/term.log.1.gz
C /var/log/dpkg.log
A /var/log/dpkg.log.1
C /var/log/lighttpd
A /var/log/lighttpd/access.log.1
A /var/log/lighttpd/error-pihole.log
A /var/log/lighttpd/error-pihole.log.2.gz
A /var/log/lighttpd/error-pihole.log.3.gz
A /var/log/lighttpd/error-pihole.log.4.gz
A /var/log/lighttpd/access-pihole.log.1
A /var/log/lighttpd/access.log
A /var/log/lighttpd/error-pihole.log.1
A /var/log/lighttpd/access-pihole.log
A /var/log/pihole-FTL.log
A /var/log/pihole.log
C /var/log/btmp
C /var/log/pihole
A /var/log/pihole/FTL.log.3.gz
A /var/log/pihole/pihole.log.1
A /var/log/pihole/pihole.log.3.gz
A /var/log/pihole/pihole.log.4.gz
A /var/log/pihole/pihole_updateGravity.log
A /var/log/pihole/FTL.log.2.gz
A /var/log/pihole/FTL.log.1
A /var/log/pihole/pihole.log
A /var/log/pihole/pihole.log.2.gz
A /var/log/pihole/pihole.log.5.gz
A /var/log/pihole/FTL.log
C /var/log/alternatives.log
A /var/log/btmp.1
C /etc
C /etc/cron.d
C /etc/cron.d/pihole
C /etc/init.d
C /etc/init.d/pihole-FTL
C /etc/lighttpd
C /etc/lighttpd/conf-available
C /etc/lighttpd/conf-available/15-pihole-admin.conf
C /etc/lighttpd/conf-enabled
A /etc/lighttpd/conf-enabled/15-pihole-admin-redirect-docker.conf
C /etc/dnsmasq.conf
C /usr
C /usr/bin
C /usr/bin/pihole-FTL
D /.piholeFirstBoot

Related Issues

I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

Environment data

Operating System: Debian
Hardware: Raspberry Pi 4 Model B
Kernel Architecture: Linux rpi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
Docker Install Info and version:
- Software source: https://download.docker.com/linux/debian/ (bullseye/stable arm64 Packages)
- Supplimentary Software: N/A

$ sudo docker version
Client: Docker Engine - Community
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Thu Feb  1 00:23:27 2024
 OS/Arch:           linux/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:27 2024
  OS/Arch:          linux/arm64
  Experimental:     true
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Hardware architecture: arm64

docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here

  pihole:
    container_name: 'pihole'
    image: 'pihole/pihole:2024.01.0'
    networks:
      - pihole
    ports:
      - '53:53/tcp'
      - '53:53/udp'
    env_file:
      - '/data/docker/pihole/env'
    restart: 'unless-stopped'
    volumes:
      - '/data/docker/pihole/etc:/etc/pihole:rw'
      - '/data/docker/pihole/dnsmasq.d:/etc/dnsmasq.d:rw'

any additional info to help reproduce

These common fixes didn't work for my issue

I have tried removing/destroying my container, and re-creating a new container
I have tried fresh volume data by backing up and moving/removing the old volume data
I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

Answer 1 · 2024-02-04T15:41:55.000Z

For what it's worth, for the beta development-v6 container, this docker diff command produces a much smaller output. Looks like the majority of the output in the current release versions is due to the s6 overlay, which is dropped entirely in development-v6 as we work towards a smaller and more efficient image

adam@devpi:/$ sudo docker diff pihole
C /usr
C /usr/bin
C /usr/bin/pihole-FTL
C /var
C /var/lib
C /var/lib/logrotate
A /var/lib/logrotate/pihole
C /var/log
A /var/log/pihole-FTL.log
A /var/log/pihole.log
C /var/log/pihole
A /var/log/pihole/pihole.log.2.gz
A /var/log/pihole/webserver.log
A /var/log/pihole/webserver.log.1
A /var/log/pihole/FTL.log.1
A /var/log/pihole/FTL.log.2.gz
A /var/log/pihole/pihole.log
A /var/log/pihole/pihole.log.3.gz
A /var/log/pihole/pihole.log.4.gz
A /var/log/pihole/pihole.log.5.gz
A /var/log/pihole/pihole_updateGravity.log
A /var/log/pihole/FTL.log
A /var/log/pihole/FTL.log.3.gz
A /var/log/pihole/pihole.log.1
C /crontab.txt
C /etc
C /etc/crontabs
C /etc/crontabs/root
C /run
A /run/crond.pid
A /run/crond.reboot
A /run/pihole
A /run/pihole-FTL.pid
C /macvendor.db

Answer 2 · 2024-02-04T16:07:02.000Z

Hi @PromoFaux,

.. as we work towards a smaller and more efficient image

Sounds nice going forward 👏

It seems the new approach is only leaving logging as an area that could benefit from some alignment with container approaches for logging 🤓

Answer 3 · 2024-02-04T16:10:07.000Z

For sure, there is always room for efficiency. If you have any suggestions, or even if you want to make pull requests, it would be welcomed.

We probably won't be expending an awful lot of effort to improve the v5 images at the moment, most of our focus is on getting V6 stable for a release (no ETA just yet!)

Answer 4 · 2024-02-04T16:21:45.000Z

Hi @PromoFaux,

We probably won't be expending an awful lot of effort to improve the v5 images at the moment, most of our focus is on getting V6 stable for a release

Understandable, I would consider logging changes "breaking" anyways - so this issue is just something to aim for going forward 🤓

Answer 5 · 2024-03-06T08:04:44.000Z

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

Answer 6 · 2024-03-06T20:09:23.000Z

Revisiting this issue, I noticed there's more than 1 service running inside the container.
So when attempting to adhere to the stdout/stderr container logging convention, the output could benefit from some context, in-order to trace errors or seprate logs afterwards 🤔

Answer 7 · 2024-04-06T08:03:58.000Z

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.