Release-upgrade Ubuntu to 22.04 with pi-hole on it, possible?

titust11 · July 26, 2022, 8:12pm

Details about my system:
I am running Ubuntu 21.10 (impish) in a Proxmox container

The issue I am facing:
When I try apt-get update it says: impish update are not available. (apparently starting July 14 is not supported anymore)
When I login the system displays the message: New release '22.04 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

The Question is:
I know pi-hole is not supported on 22.04 due to installation issues, but now that it is installed, can I go ahead and upgrade the version in the container? Will pi-hole still work? Did anyone try this?
Thanks

jfb · July 26, 2022, 8:24pm

titust11 · July 26, 2022, 8:42pm

LOL Aaah, common man this is new, a few weeks ago I checked myself and 22 was not there.
I even tried to install 22.04 and I could not do it. The installation did not begin in the Welcome screen since the button cannot be selected with enter (or any other key)

yubiuser · July 26, 2022, 10:52pm

This is an external issue, but we worked around it.

github.com/pi-hole/pi-hole

Convert installer whiptail to dialog

pi-hole:development ← pi-hole:tweak/dialog

opened 03:40AM - 29 Jun 22 UTC

dschaper

+461 -283

## Thank you for your contribution to the Pi-hole Community! Please read the… comments below to help us consider your Pull Request. We are all volunteers and completing the process outlined will help us review your commits quicker. **Please make sure you** 1. Base your code and PRs against the repositories developmental branch. 2. [Sign Off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits as we enforce the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions --- - **What does this PR aim to accomplish?:** Ubuntu 22 has issues with `whiptail` invocation through our installer script. Replace whiptail with dialog. --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code and I have tested my changes. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) --- - [x] I have read the above and my PR is ready for review. _Check this box to confirm_

system · August 16, 2022, 10:53pm

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.