-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removal of /s6-init
breaks entrypoint
overrides
#1701
Comments
Thanks, I'll leave this open in case someone else has a similar issue - though I'm not sure how many folk were doing this. Interesting way around an issue, though. Any reason why you're not just using a volume mount for /etc/dnsmasq.d? |
An alternative solution for you, as i've just learned about the existence of this config option Setting via the web interface stores it in the config file like so: dnsmasq_lines = [
"server=/61.10.in-addr.arpa./127.0.0.1#953",
"server=/an.example.invalid./127.0.0.1#953"
] ### CHANGED, default = [] This could also be set by the environment variable |
@PromoFaux have you tried that - because the "=" breaks it. |
It's "permanent" (in this environment) and the VM's that run pihole only have ephemeral storage, so, rather than giving it a gluster volume for that tiny little file - I have been creating it on start.
|
Yeah, sorry - that's what I meant by:
Lets see what DL comes back with... |
AH! Sorry! Yeah - I've tried (what I think is?) every possible iteration of single, double quotes, list/sequence, mapping - I just can't get anything past the "=" |
The value is passed to the container. Inside the container there will be a variable with the value, like:
But FTL is not correctly parsing values with |
@rdwebdesign Do you want me to create a new ticket for that? |
No need for another issue. We are aware of the issue and we will fix it when we have the time to dig into the code. Just be patient. |
@rdwebdesign appreciate it - thank you. |
This is an FTL issue somewhere around |
Fix for the env setting at pi-hole/FTL#2204 |
Same issue as #1718 |
@troykelly - the latest tag should fix this issue. Please let us know! https://github.com/pi-hole/docker-pi-hole/releases/tag/2025.02.2 |
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-init
as 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.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.
The text was updated successfully, but these errors were encountered: