Alpine linux support?

ajp2k17 · January 30, 2019, 10:02am

How about Alpine Linux support now that is has a build for the Pi?

EDIT: ok, looks like it had Pi-support even before 3.9.0... but still.

Leptopoda · February 22, 2019, 5:33am

+1 for me
Alpine is small and more resource efficient. An official Alpine install would lead to a switch from Debian to Alpine in the official docker image.

See: @diginc Docker Pi-hole on Alpine base aarch64. QoS priority+ cake-sqm

As mentioned in the article the docker image would shrink a lot...

ilpianista · April 15, 2020, 3:20pm

Hi, FYI I got pihole working on alpine 3.10. I started from scratch, but my work has been inspired by @deftdawg patch and by the last_alpine_commits branch and it's available here and here.

emceelamb · April 23, 2020, 10:16pm

Awesome. I was able to install Pihole on alpine aarch64 with your fork, but I haven't been able get it properly configured. Lighthttpd doesn't seem to be in apk for aarch so I installed Pihole without the web interface. Now I can't get pihole-FTL to start up the dns. If I manually start dnsmasq Was there any extra steps you had to do to set up the dns? I don't necessarily need the web gui.

Thanks!

ilpianista · April 24, 2020, 8:42am

For me it's working, but there's only one problem: ip -oneline is broken in alpine >= 3.9 and thus the discovery of the interfaces fails. I manually edited /etc/pihole/setupVars.conf to set the PIHOLE_INTERFACE variable.

yiding · June 19, 2020, 8:06pm

Trying your fork on alpine 3.11

I think ip -online is fixed on 3.11, so that should be a non issue.

One issue I ran into is that the blocklist update script (gravity.sh) generates the sqlite input with an extra empty line between each entry, which causes the blocklist update to fail. Installing gnu sed to replace busybox sed fixed this.

Any plans to upstream the alpine support?

malbeth · August 19, 2020, 3:12pm

I managed to manally install Pi-hole FTL & Admin on Alpine Linux Install on "non-supported" distro?

@yiding I got the gravity update script working with only a few minor patches.

mcrute · May 10, 2025, 7:42pm

I have 6.1 packaged for Alpine. See my comments over on Pihole v6 beta baremetal on Alpine?

yubiuser · May 10, 2025, 7:56pm

We are likely going to support installation on bare metal Alpine soon

github.com/pi-hole/pi-hole

feat: add Alpine Linux support

development ← jrittenh:alpine

opened 02:07AM - 18 Mar 25 UTC

jrittenh

+285 -10

- Add Alpine Linux package manager detection - Implement meta package for Alpin…e dependencies - Add Alpine-specific paths and service management - Handle Alpine cleanup in uninstaller ## 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 3. [Sign](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all your commits as they must have verified signatures 4. File a pull request for any change that requires changes to [our documentation](https://docs.pi-hole.net/) at our [documentation repo](https://github.com/pi-hole/docs) --- **What does this PR aim to accomplish?:** This PR adds support for Alpine as a target installation OS. **How does this PR accomplish the above?:** Minimal changes following the other OS build processes, with definitions specific to Alpine **Link documentation PRs if any are needed to support this PR:** --- **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)) 6. I have checked that another pull request for this purpose does not exist. 7. I have considered, and confirmed that this submission will be valuable to others. 8. I accept that this submission may not be used, and the pull request closed at the will of the maintainer. 9. I give this submission freely, and claim no ownership to its content. --- - [x] I have read the above and my PR is ready for review. *Check this box to confirm*

(Even this PR looks abandoned, we'll pick it up one way or the other)

mcrute · May 10, 2025, 8:24pm

Oh cool. I'll take a look at that PR but at a quick glance I would suggest not taking that specific approach. There's a lot of little things needed to fit nicely into the Alpine package ecosystem and it looks like that patch doesn't fully solve the issues. Take a look at my downstream package. I'd really appreciate review from Pi-hole maintainers on that and would be willing to contribute my patches upstream to the project.