Versions
Core version is v6.0 (Latest: v6.0)
Web version is v6.0 (Latest: v6.0)
FTL version is v6.0 (Latest: v6.0)
Platform
- OS and version: Debian GNU/Linux 11
Expected behavior
Anybody with old entrypoint overrides will be calling /s6-init as the last command to allow the container to continue to start as intended, ie:
entrypoint: |
/bin/sh -c
"echo 'server=/61.10.in-addr.arpa./127.0.0.1#953' > /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/an.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/another.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/yet.another.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
exec /s6-init"
Actual behavior / bug
Without the former startup file, pihole keeps restarting.
Steps to reproduce
Steps to reproduce the behavior:
- Override entrypoint on container
- Start container
Debug Token
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I can't see anything announced that the startup entrypoint was changing, but using the new entrypoint resolves the issue.
To resolve this issue, use start.sh
entrypoint: |
/bin/sh -c
"echo 'server=/61.10.in-addr.arpa./127.0.0.1#953' > /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/an.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/another.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
echo 'server=/yet.another.example.invalid./127.0.0.1#953' >> /etc/dnsmasq.d/02-custom.conf &&
exec /usr/bin/start.sh"
Yes, this isn't the greatest hack - but there's no way to persist minor config settings like this without shared volumes, so creating this file on startup is the only real solution.
Versions
Core version is v6.0 (Latest: v6.0)
Web version is v6.0 (Latest: v6.0)
FTL version is v6.0 (Latest: v6.0)
Platform
Expected behavior
Anybody with old entrypoint overrides will be calling
/s6-initas the last command to allow the container to continue to start as intended, ie:Actual behavior / bug
Without the former startup file, pihole keeps restarting.
Steps to reproduce
Steps to reproduce the behavior:
Debug Token
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I can't see anything announced that the startup entrypoint was changing, but using the new entrypoint resolves the issue.
To resolve this issue, use
start.shYes, this isn't the greatest hack - but there's no way to persist minor config settings like this without shared volumes, so creating this file on startup is the only real solution.