Closed weitzner closed 3 years ago
Hi, The official upstream use "obsolete" versions 2021-10-27T07:54:40.614516586Z Pi-hole version is v5.3.1 (Latest: v5.6) 2021-10-27T07:54:40.651880588Z AdminLTE version is v5.5.1 (Latest: v5.8) 2021-10-27T07:54:40.680463140Z FTL version is v5.8.1 (Latest: v5.11) 2021-10-27T07:54:40.683035577Z Container tag is: pihole/pihole:master-arm64-buster
The official nightly build is "obsolete" too 2021-10-27T12:40:11.815788266Z Pi-hole version is development v5.4-50-g8713135 (Latest: v5.6) 2021-10-27T12:40:11.823482388Z AdminLTE version is devel v5.6-74-gae17a48 (Latest: v5.8) 2021-10-27T12:40:11.827505836Z FTL version is v5.11 (Latest: v5.11) 2021-10-27T12:40:11.827968102Z Container tag is: nightly
I can easily upgrade to FTL v5.11, I have done some checks and it works fine. Latests verssions may need some coordinated and additional work Update from upstream are now in the hub.
A nightly flavour based in upstream was added in the hub, it takes around 20 minutes in CI ;)
Added an edge version from upstream git
2021-10-27T14:56:10.486413895Z Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf 2021-10-27T14:56:10.570857473Z Pi-hole version is in detached HEAD state at v5.6 (Latest: v5.6) 2021-10-27T14:56:10.611627360Z AdminLTE version is in detached HEAD state at v5.8 (Latest: v5.8) 2021-10-27T14:56:10.639220539Z FTL version is v5.11 (Latest: v5.11) 2021-10-27T14:56:10.642423249Z Container tag is: pihole/pihole:master-arm64-buster
Awesome! Thanks so much, Juan. I've already updated my pi 🙂
It looks like the docker hub image isn't syncing up with the pi-hole upstream - is this still something that needs to be done manually?
I just add a dispatch event to CI, to manually trigger the build process.
Thanks for putting together this image - I use it and it works well. Are you planning to pull the upstream pihole image to update this? It would be great if this generally kept pace with upstream.