-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Release/v4.0 #300
Release/v4.0 #300
Conversation
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
* Removed some old switch statements from alpine no longer required * Limit parallel tests to 2 to help prevent test failure caused by race condition starting parallel tests/containers * Began introducing a new ENV NO_SETUP to skip the majority of startup script 'setup' functions eventually Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
…ast, starting on new deploy Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Repo naming changes
Signed-off-by: Adam Hill <adam@diginc.us>
…t works Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
…mments) Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
@diginc I notice there hasn't been a push to Docker Hub yet, if you plan to release an alternate tag to test prior to pushing across to the latest branch please let me know, happy to give it a try and report any issues back. |
@nightah The new image is I will get the old image pushed with an update as well, after the new one is released. This maybe it's last update just to let people know to change their image name to the new official image which will get on going updates. |
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Signed-off-by: Adam Hill <adam@diginc.us>
Does this need an approval? |
@diginc thanks for the heads up. I've re-tested and found a small problem with populating the DNS server(s). I have the following configuration set at the moment:
When I use the latest version provided it will work on first boot with the migrated config, however, from there on out if I issue a docker restart pihole the DNS server is removed and will remain blank. Here's what the startup log looks like on the first boot:
And the subsequent log after another restart where it fails:
Let me know if you want me to do a little more digging, if I can get you more information. I have overcome the issue for now by just setting |
@nightah thanks for the report, I reproduced your problem and am pushing the fix right now. Merging to master to get the README updated on the main repository page since v4.0 is announced to the public and there are some important updates in the readme for that. |
Since piholeFTL test properly spins down it's no longer necessary to kill it. He's dead Jim Merge pi-hole#300, added `piholeFTL test` to the startup sequence to replace dnsmasq as a dependency for validate_env and gravity.sh. kill -9 was kept as a work around to a standing issue that `piholeFTL test` didn't spin down on it's own. This was fixed in pi-hole/FTL#1067, landed on Apr 14 2021 and confirmed working, as evinced by pi-hole#834 which was filed the same day it that fix landed. Signed-off-by: D.Rect <48034372+DistractionRectangle@users.noreply.github.com>
All changes related to v4.0 upgrade, replacing prerelease branch #289
A few of the bigger recently commited changes:
setup_config
function should address some permission problems previously had by people using volumessetup_config
setupVars file re-writing should handle upgrading from old data by writing required new variables