Hi @Nathan_Brin,
It’s normal for it not to be updated this way, as we need to use the “Docker way” of doing so. Fortunately, thanks to @laxdog, we already have an updated Rockon for pi-hole that you can install manually.
Indeed, clicking the “Update” button on the Rockon page only refreshes the list of approved Rockon, which the updated pi-hole has not reached yet.
The steps to install it are described here:
- Create the following directory:
/opt/rockstor/rockons-metastore - Place the pi-hole.json there. Here’s the file:
rockon-registry/pi-hole.json at bc9b8b8fdcb7bde573cdd7f7fc0795852ef4b095 · rockstor/rockon-registry · GitHub
Now, when you refresh the list of available Rock-on by clicking the “Update” button, you should see the new one as well. We now need to proceed with the Uninstall of the current pi-hole and install of the new one. No worries, though, as you can simply re-use the same shares you are currently using for the pihole Rockon and you will keep all the settings you had set.
- Turn current pihole Rock-on off on the Rockstor webUI
- Due to the specificity of pihole, here things differ depending on your setup:
a. you set both of your DNS servers on your router to your pi-hole machine: Pull new image:docker pull pihole/pihole:latest. Then go to step 3.
b. you kept one non-pihole DNS server on your router: go to step 3 directly. - Uninstall Rock-On from webUI
- Install the new Rock-on from the webUI using the same pi-hole config volume.
We had a discussion about this update process there if you want more info:
Everything should now be working ok. The only thing to make sure of with this Rock-on, is that you you still have a DNS server up (non-pihole) while the Rock-on is off otherwise you will not be able to pull the updated pihole image.
Hope this helps,