My Pihole updated in the last hour within Docker, and now isnt resolving DNS.
DNS service not running FTL offline
I can enable from the menu, but it starts then stops.
Googling hasn't found anything in the last hour so asking here if anyone else going through this
(This is the second docker container that's mucked up this week due to updates, Qbitorrent being the other)
Posted Feb 16, 2021, 11:02 PM UTC
Well, stop updating stuff for no reason. Revert to the previous working version. That’s the beauty of containers — they are disposable monolithic immutable entities.
Ive had this system running a couple of years now with no issue till two this week.
Unfortunalty im a ludite just using the GUI console and following tutorials to get them working. Revertign is beyond me at the moment. I tried witht eh Qbitorrent item I had, exporting, downloadign the last known good, ediding the JSOn file for the new imagew,
didnt work. So im floundering at the moment.
I'll do some more research when I have time, busy at work atm
I started out with Docker on my Synology too but I found it to be more reliable to run Linux Hyper-V VMs on an old laptop for each service I'm using. Performance is better, maintenance is cake since its just Ubuntu server without GUI and I backup the VHDs to my Synology.
I know this doesn't solve your question but I can highly recommend it. Its pretty addicting so now I'm looking for an actual rack mountable server with dual Xeons.
Seems like an issue with FTL 5.7, i heard people saying the same thing