jwr1 to [email protected] • 30 days agoIntroducing Pi-hole v6pi-hole.netmessage-square61fedilinkarrow-up1373arrow-down10cross-posted to: [email protected]
arrow-up1373arrow-down1external-linkIntroducing Pi-hole v6pi-hole.netjwr1 to [email protected] • 30 days agomessage-square61fedilinkcross-posted to: [email protected]
minus-squareddhlinkfedilinkEnglish27•30 days agoBe careful upgrading Docker versions, it has breaking changes. https://registry.hub.docker.com/r/pihole/pihole/
minus-squarefmstratlinkfedilinkEnglish7•edit-229 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-square@[email protected]linkfedilinkEnglish2•29 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.