Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update pihole/pihole Docker tag to v2021 #101

Merged
merged 1 commit into from
Dec 15, 2021
Merged

Update pihole/pihole Docker tag to v2021 #101

merged 1 commit into from
Dec 15, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 17, 2021 •
edited
Loading

WhiteSource Renovate

This PR contains the following updates:

Package Update Change
pihole/pihole major v5.8 -> 2021.11

Release Notes

pi-hole/docker-pi-hole

v2021.11

Compare Source

Docker specific changes

Pi-hole FTL Changes

  • None

Pi-hole Core Changes

  • None

Pi-hole Web Changes

  • None

New Contributors

Full Changelog: pi-hole/docker-pi-hole@2021.10.1...2021.11

v2021.10

Compare Source

It must be October somewhere in the world, right?

Breaking Changes:
  • Should be no showstoppers, but keep in mind internal components have been version-bumped (Pi-hole FTL v5.10.2, Web v5.7 and Core v5.5) Please ensure you have read the release notes for those before updating!
Docker Specific Changes:
Pi-hole FTL changes:
  • Handle TTL for blocked queries separately #​1173
  • Improvements based on static-analysis of source code #​1172
  • Add special handling of iCloud Private Relay domains #​1171
  • Fix virtual interface address determination #​1170
  • Add handling for pi.hole.<local_domain> and <hostname>.<local_domain> #​1169
  • Simple maintenance improvements #​1167 (thanks @​a1346054)
  • Add PIHOLE_PTR=HOSTNAME option #​1164
  • Tweak special domain handling #​1163
  • Change FTL database permission to 664 #​1162 (thanks @​yubiuser)
  • Add further cache metrics #​1152
  • Update embedded dnsmasq to v2.87test3
Pi-hole Core Changes:
Pi-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 until 2021.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 the dev branch of this repo, and the development/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:

  • Important: Read the release notes. Sometimes you will need to make changes other than just updating the image
  • Pull the new image
  • Stop and remove the running Pi-hole container
    • If you care about your data (logs/customizations), make sure you have it volume-mapped or it will be deleted in this step.
  • Recreate the container using the new image

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:
  • None
Docker Specific Changes:
  • 3865e77 - Introduce internal PIHOLE_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 container
  • 88518b0 & 56f4933 - Inject the container tag into the web interface footer
  • Set FTL REPLY addresses instead of setupVars.conf. #​902
  • Improve Docker Healthcheck: Shorten dig output #​905
Pi-hole Core Changes:
Pi-hole Web changes:
Pi-hole FTL changes:

Configuration

📅 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.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/pihole-pihole-2021.x branch from b942c0d to e82192a Compare November 27, 2021 01:50
@itobey itobey merged commit 4374cc3 into master Dec 15, 2021
@renovate renovate bot deleted the renovate/pihole-pihole-2021.x branch December 15, 2021 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@itobey @renovate-bot