Releases: pi-hole/docker-pi-hole
Releases · pi-hole/docker-pi-hole
v4.3
Includes the following versions of upstream software:
- Pi-hole v4.3 - release notes
- AdminLTE v4.3 - release notes
- FTLDNS v4.3 - release notes
v4.2.2-1
Includes the following versions of upstream software:
- Pi-hole v4.2.2 - release notes
- AdminLTE v4.2 - release notes
- FTLDNS v4.2.3 - release notes
No docker image changes
v4.2.2
Includes the following versions of upstream software:
- Pi-hole v4.2.2 - release notes
- AdminLTE v4.2 - release notes
- FTLDNS v4.2.2 - release notes
Docker Issues resolved:
- #316 - Got rid of ServerIP ENV requirement, default block mode no longer requires this
- #408 - DNS2=no didn't properly ignore default DNS setup
- #419 - New function for default ad list creation was not triggered correctly in 4.2.1
- #364 - Webpassword should not change on re-creation if volume has it set before
Docker Pi-Hole v4.2
Includes the following versions of upstream software:
- Pi-hole v4.2 - release notes
- AdminLTE v4.2 - release notes
- FTLDNS v4.2 - release notes
v4.1.1
Docker Pi-Hole v4.1.1
Includes the following versions of upstream software:
- Pi-hole v4.1.1
- AdminLTE v4.1.1
- FTLDNS v4.1.2 (formerly v4.1.1)
Breaking Changes
--cap-add=NET_ADMIN
This previously optional argument is now required or strongly encouraged- Starting in a future version FTLDNS is going to check this setting automatically
--dns=127.0.0.1 --dns=1.1.1.1
The second server can be any DNS IP of your choosing, but the first dns must be 127.0.0.1- A WARNING stating "Misconfigured DNS in /etc/resolv.conf" may show in docker logs without this.
Bug Fixes:
- No longer uses FTLDNS debug mode, back to no-daemon (saves writing logs to SD cards for RBPis)
- Blocks
pihole -up
properly again
Improvements:
- Docker run documentation improved for
--dns
and--cap-add
- Added a check for having container's DNS setup in the recommended way