Update ftl-build container

[DL6ER]

What does this implement/fix?

We add the dnspython package to be able to write more complicated DNS tests on the CI.
Furthermore, we

• update the mbedtls library to its most recent version,
• update the entire build container to alpine:3.22 released yesterday, and
• use arm runners for arm targets to drastically improve build time:

This PR

(ignore the RISCV64 job)

master

---

Related issue or feature (if applicable): N/A

Pull request in docs with documentation (if applicable): N/A

---

By submitting this pull request, I confirm the following:

1. I have read and understood the contributors guide, 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.
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
5. I have squashed any insignificant commits. (git rebase)

Checklist:

• The code change is tested and works locally.
• I based my code and PRs against the repositories developmental branch.
• I signed off all commits. Pi-hole enforces the DCO for all contributions
• I signed all my commits. Pi-hole requires signatures to verify authorship
• I have read the above and my PR is ready for review.

[yubiuser]

Compiling readline failed.

[DL6ER]

I restarted the armv8 build a few times now, it fails in various different libraries with a serious compiler issues. Seems the most recent stable (!) Alpine release is having issues on armv8.

[dschaper]

Running Actions on this branch at https://github.com/pi-hole/docker-base-images/actions/runs/14956211804

[dschaper]

The failing or timeout builds all fail at this step:

 #14 1233.8 195/202 ✓ Internal IP -> name resolution works (UDP IPv4)
#14 1234.5 196/202 ✓ Internal IP -> name resolution works (UDP IPv6)
#14 1235.2 197/202 ✓ Internal IP -> name resolution works (TCP IPv4)
#14 1236.0 198/202 ✓ Internal IP -> name resolution works (TCP IPv6)

[DL6ER]

The step following on this is the API verification which is quite an extensive test. However, even with CPU emulation it should take at most a few seconds. But it is definitely already an improvement...

[DL6ER]

@dschaper how have you been able to re-trigger a build here (were you)? I just saw that the builds are a long time ago and it seems there is no option to try again now

[dschaper]

Manual trigger on the workflow, pick the branch from the PR.

[DL6ER]

I decided to push another commit to this PR, the non-emulated have already finished running. Keeping my fingers crossed

[dschaper]

Doesn't look gut.

https://github.com/pi-hole/docker-base-images/actions/runs/15085576334/job/42407670949

[DL6ER]

@yubiuser @dschaper Build containers fixed. Follow-up PR to get the necessary changes into FTL is pi-hole/FTL#2477 once we have a tag here and can it include over there. The PR description has been updated to reflect the changes in this PR