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.

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

chore(deps): update container image pihole/pihole to v2022.04.3 #124

Merged
merged 1 commit into from
Jun 4, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2022

Mend Renovate

This PR contains the following updates:

Package Update Change
pihole/pihole major v5.8.1 -> 2022.04.3

Release Notes

pi-hole/docker-pi-hole

v2022.04.3

Compare Source

Docker specific changes

New Contributors

Full Changelog: pi-hole/docker-pi-hole@2022.04.2...2022.04.3


This release also contains updates for the 3 main components (FTL v5.15, Web v5.12, and Core v5.10), Changelogs below:

What's Changed (FTL 5.15)

New Contributors

Full Changelog: pi-hole/FTL@v5.14...v5.15


What's Changed (Web 5.12)

New Contributors

Full Changelog: pi-hole/web@v5.11...v5.12


What's Changed (Core 5.10)

New Contributors

Full Changelog: pi-hole/pi-hole@v5.9.1...v5.10

v2022.04.2

Compare Source

Important note:

You may run into issues running 2022.04 and later on buster-based host systems due to a known issue with Seccomp. The first recommendation is to upgrade your host OS to bullseye, which includes a more up to date (and fixed) version of libseccomp2.

If you absolutely cannot do this, some users have reported success in updating libseccomp2 via backports. You can try this workaround at your own risk

What's Changed

New Contributors

Full Changelog: pi-hole/docker-pi-hole@2022.04.1...2022.04.2

v2022.04.1

Compare Source

This release should fix the capabilities issues once and for all. If you found you needed to set CAP_NET_ADMIN or set DNSMASQ_USER to root in recent releases, and would rather not have - you should now be able to unset those.

What's Changed

Full Changelog: pi-hole/docker-pi-hole@2022.04...2022.04.1

v2022.02.1

Compare Source

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923479

What's Changed

Full Changelog: pi-hole/docker-pi-hole@2022.02...2022.02.1


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - 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 Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/pihole-pihole-2022.x branch from ac8d1f5 to 6b858b2 Compare April 21, 2022 01:02
@renovate renovate bot changed the title chore(deps): update container image pihole/pihole to v2022.04.2 chore(deps): update container image pihole/pihole to v2022.04.3 Apr 21, 2022
@axeII axeII merged commit 987d9ec into main Jun 4, 2022
@paul-the-alien paul-the-alien bot deleted the renovate/pihole-pihole-2022.x branch June 4, 2022 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants