I recently discovered that docker pihole doesn't support the MIPS architecture that my device uses and or the FTL engine. I know people have managed to run it before tho and this user https://www.reddit.com/r/pihole/comments/fnhfb8/pihole_for_mips_ci20/ managed to run it a few years ago (I don't care if I have to use an older version) so I was wondering if any of you guys had any idea how to make it work with docker?
I've posted this to multiple forums without any interactions so I'm really praying that someone here can give me an answer, even if it is that what I'm trying to do is impossible.
I think it is impossible to explain what is different. There are so many changes and improvements.
Using that version would be like using a complete different software and we won't be able to provide support.
You would need to use the correct version for all 3 components (pihole core, FTL and web interface).
thank you so much for you help, i kinda need this to work so I'll give it a try just for the sake of it.i feel like my only reasonable next the step would be rewriting a newer version to work.
Building a Docker image for mips arch may be more diffcult to achieve. Linux OSs on Docker seem to have no support for mips when checking for current releases like Ubuntu 22.04/Jammy or Debian 11/Bullseye
But then, maybe I did not look in all the right places.
there are debian docker containers that support Mips already working, my current plan is trying to set up the older version of ftl and pi-hole on this. would it be possible to compile pihole-ftl this way?
OpenWRT is not an OS supported by Pi-hole, and MIPS is not officially supported by Docker.
You'd have to try yourself.
In a resource-restricted system like a router, I'd probably drop Docker and try the binary compilation approach first.
Note that pihole-FTL is a tailored version of dnsmasq - an existing dnsmasq instance would conflict with Pi-hole.
Getting the OpenWRT community involved seems also like a good idea (but I guess you've already tried that).
is binary compilation as scary as it sounds?
i was plannnig on using mcvlan to bridge the networks, not have them as one. is dnsmasq still an issue? tbh ill just make a custom version of openwrt without dnsmasq.