Modify 0-on-boot.sh to consider pihole

[jetuser]

If you're running pihole on a UDM, oftentimes if the UDM updates the core os the cached apt packages you have locally will not install correctly (due to the OS updating) requiring you to go back and update the repository to get new packages to re-install systemd container to get machinectl back.

Now obivously if you've updated your dns config to point to your pihole and systemd-container is down the automated reinstall won't work and you'll black hole your network. Can someone suggest a modification to the boot script to temporarily flip the dns back to a public dns to update/re-cache the necessary packages before re-enabling the pihole container and then re-pointing back to it?

As it stands, I have to manually flip the dns back to public and manually update/re-install systemd-container before i can get my pihole back up and running.