jwr1@kbin.earth to Selfhosted@lemmy.world · 4 days agoIntroducing Pi-hole v6pi-hole.netexternal-linkmessage-square59fedilinkarrow-up1366arrow-down10cross-posted to: selfhosted@lemmy.worldselfhost@lemmy.ml
arrow-up1366arrow-down1external-linkIntroducing Pi-hole v6pi-hole.netjwr1@kbin.earth to Selfhosted@lemmy.world · 4 days agomessage-square59fedilinkcross-posted to: selfhosted@lemmy.worldselfhost@lemmy.ml
minus-squareddh@lemmy.sdf.orglinkfedilinkEnglisharrow-up27·4 days agoBe careful upgrading Docker versions, it has breaking changes. https://registry.hub.docker.com/r/pihole/pihole/
minus-squarefmstrat@lemmy.nowsci.comlinkfedilinkEnglisharrow-up6·edit-23 days agoWhew, this is why I pin on sha256. I fear for the latest crowd. Edit: At least it seems updating the container doesn’t break things: Replacing any v5 image (2024.07.0 and earlier) with a v6 image will result in updated configuration files. These changes are irreversible.
minus-squareJustEnoughDucks@feddit.nllinkfedilinkEnglisharrow-up2·2 days agoLive on the edge Pin to develop
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkEnglisharrow-up2·3 days agoI don’t use pihole, but everything I use is pinned by major release version. No problem yet with surprise breakage.
Be careful upgrading Docker versions, it has breaking changes.
https://registry.hub.docker.com/r/pihole/pihole/
Whew, this is why I pin on
sha256. I fear for thelatestcrowd.Edit: At least it seems updating the container doesn’t break things:
Live on the edge
Pin to
developI don’t use pihole, but everything I use is pinned by major release version. No problem yet with surprise breakage.