Pihole container on Raspberry Pi Zero W (armv6) keeps restarting

Product support
1

Hi!
As title, my Pihole container on my Raspberry Pi Zero W (armv6) keeps restarting.
I followed tutorial from your blog

setting also env variables (to use eth0 interface).
Can anybody help me, please?
Thank you!

These are pihole logs:

10.09.19 12:16:04 (+0200) Restarting service ‘pihole sha256:d64b6ade6861ff81088c6733b41eae7b02ec8abfef4723ec29583587880f7168’
10.09.19 12:15:05 (+0200) [s6-finish] sending all processes the KILL signal and exiting.
10.09.19 12:16:04 (+0200) [s6-init] making user provided files available at /var/run/s6/etc…exited 0.
10.09.19 12:16:05 (+0200) [s6-init] ensuring user provided files have correct perms…exited 0.
10.09.19 12:16:05 (+0200) [fix-attrs.d] applying ownership & permissions fixes…
10.09.19 12:16:05 (+0200) [fix-attrs.d] 01-resolver-resolv: applying…
10.09.19 12:16:05 (+0200) [fix-attrs.d] 01-resolver-resolv: exited 0.
10.09.19 12:16:05 (+0200) [fix-attrs.d] done.
10.09.19 12:16:05 (+0200) [cont-init.d] executing container initialization scripts…
10.09.19 12:16:05 (+0200) [cont-init.d] 20-start.sh: executing…
10.09.19 12:16:05 (+0200) [cont-init.d] 20-start.sh: exited 267.
10.09.19 12:16:05 (+0200) [cont-finish.d] executing container finish scripts…
10.09.19 12:16:05 (+0200) [cont-finish.d] done.
10.09.19 12:16:05 (+0200) [s6-finish] syncing disks.
10.09.19 12:16:06 (+0200) [s6-finish] sending all processes the TERM signal.
10.09.19 12:16:09 (+0200) [s6-finish] sending all processes the KILL signal and exiting.
10.09.19 12:16:13 (+0200) Service exited ‘pihole sha256:d64b6ade6861ff81088c6733b41eae7b02ec8abfef4723ec29583587880f7168’

2

Project (with 2 containers) has been correctly pushed

image
image.png895×251 11.9 KB

3

Env variables

image
image.png1165×388 17.2 KB

4

Hi @lewix,

I think that RPi Zero doesn’t have enough RAM to run this project.

That’s why we advise using this project with a RPi2 minimum: https://www.balena.io/blog/deploy-network-wide-ad-blocking-with-pi-hole-and-a-raspberry-pi/#hardwarerequired

6

Hi @spanceac,
ok may be a cause, but it’s strange: i run pihole on my pizero using official installer (no docker) without issues.

7

Hi @lewix ,

We can have a look and see if something is going on, if you’d like (although I believe as Sebastian says, memory is probably the issue here). If you let us know the dashboard URL or UUID of the device, we’ll take a further look.

Best regards,

Heds

9

Hi @hedss,
thanks!

UUID of the device: 38186397d3586481b127e04c77fd9a4a
I enabled support access.
Let me know if you need more infos, and thank you again.

Lewix

10

Hi @lewix,

I’ve just had a quick look and it seems like it’s actually the PiHole service itself that is restarting, and it’s not a memory issue. I’ve a vague recollection that this might not actually work on the Pi Zero, which is why the author has explicitly stated the RPi variants in the blog post. I’m going to ping him and see if there was a specific reason.

We’ll get back to you as soon as we have an answer.

Best regards,

Heds

13

Thank you @hedss!

15

@hedss,
pihole docker mantainer confirms exists an issue about armel build for pi zero and (Coincidentally :upside_down_face:) today has just been open a pull request to fix it.


Lewix

16

Hi @lewix ,

Great, that’ll be the reason then! Chris is off today, but now you’ve mentioned it, I’m pretty certain that was the reason. Would also explain the self-termination!

Hopefully the patch will be merged really soon!

Best regards,
Heds

18

Hi @hedss,
i cloned a branch repo of pihole with armel fix (non merged yet in master) and I can confirm pihole is working on my pizero :+1:
My temporary repo (maybe someone needs it) is here
https://hub.docker.com/r/lewixlabs/pihole-pizero

image

19

Hi @lewix,

That’s great news, and thanks very much for letting us know! Hopefully this will be merged in the master branch soon!

Best regards,

Heds