Update pihole/pihole Docker tag to v2021 #101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.8
->2021.11
Release Notes
pi-hole/docker-pi-hole
v2021.11
Compare Source
Docker specific changes
Pi-hole FTL Changes
Pi-hole Core Changes
Pi-hole Web Changes
New Contributors
Full Changelog: pi-hole/docker-pi-hole@2021.10.1...2021.11
v2021.10
Compare Source
Breaking Changes:
Docker Specific Changes:
install.sh
to always install latest released Pi-hole unless otherwise indicated by env vars pi-hole/docker-pi-hole@ca69e29amd64
/buster
, and switch to using nativedocker/build-push-action@v2
/buildx
actions to build and deploy the multiarch image pi-hole/docker-pi-hole@7624fc3 (see https://github.com/pi-hole/docker-pi-hole/issues/735)linux/arm/v6
to build pi-hole/docker-pi-hole@bc545b6linux/ppc64le
to build pi-hole/docker-pi-hole@c371768Pi-hole FTL changes:
pi.hole.<local_domain>
and<hostname>.<local_domain>
#1169PIHOLE_PTR=HOSTNAME
option #1164664
#1162 (thanks @yubiuser)Pi-hole Core Changes:
local-ttl
from set of defaultdnsmasq
options #4339 @DL6ERDNS_FQDN_REQUIRED
andDNS_BOGUS_PRIV
to setupVars.conf during installation #4327 @yubiuserINSTALLER_DEPS
have been installed #4325 @yubiuserPi-hole Web changes:
v2021.09
Compare Source
Previously, we have picked a version number of one of the internal components (most recently, FTL) and applied that to the docker container's tag. However, this sometimes causes confusion between users, but also developers (when we are not sure what to tag a docker release if FTL's version number has not changed)
Going forward, we will use a
year.month[.revision]
to tag docker releases with. To tag a new image, it is as simple as looking at the calendar to decide what the tag name should be. We will always try to leave any major changes until a new month rolls over. e.g if Pi-hole v6 were to be released in 2 weeks time, it would not be in the docker image until2021.10
(that said, we can also tag pre-release versions for those that are itching to get onto the bleeding edge. This also gives us chance to make sure that none of the core Pi-hole changes break how the container operates.There will always be a
:nightly
tag, which is built every night based on thedev
branch of this repo, and thedevelopment
/devel
branches of the three components, for those who really want to live on the edge - but we don't recommend running this in production.We have also noticed that a lot of people use Watchtower or Portainer to keep their Pi-hole containers up to date. For the same reason we don't provide an auto-update feature on a bare metal install, you should not have a system automatically update your Pi-hole container. Especially unattended. As much as we try to ensure nothing will go wrong, sometimes things do go wrong - and you need to set aside time to manually pull and update to the version of the container you wish to run. The upgrade process should be along the lines of:
Pi-hole is an integral part of your network, don't let it fall over because of an unattended update in the middle of the night.
Breaking Changes:
Docker Specific Changes:
3865e77
- Introduce internalPIHOLE_TAG
variable so that we can see what tag the container is...388f0f0
- Disable some more pihole functions when run from within docker, Inject a message into the debug output that lets us know it's been run in a docker container88518b0
&56f4933
- Inject the container tag into the web interface footerPi-hole Core Changes:
Pi-hole Web changes:
Pi-hole FTL changes:
reply
type Regex extension: Specify reply type pi-hole/FTL#1159dnsmasq
to version 2.86Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.