jwr1 to [email protected] • 2 months agoIntroducing Pi-hole v6pi-hole.netmessage-square59fedilinkarrow-up1365cross-posted to: [email protected][email protected]
arrow-up1365external-linkIntroducing Pi-hole v6pi-hole.netjwr1 to [email protected] • 2 months agomessage-square59fedilinkcross-posted to: [email protected][email protected]
minus-squareddhlinkfedilinkEnglish26•2 months agoBe careful upgrading Docker versions, it has breaking changes. https://registry.hub.docker.com/r/pihole/pihole/
minus-squarefmstratlinkfedilinkEnglish5•edit-22 months 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•2 months 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:
I don’t use pihole, but everything I use is pinned by major release version. No problem yet with surprise breakage.