pi-hole-multiarch:v3.2.1_debian_armhf not starting on Pi B #218

muddlethrough · 2018-01-15T22:44:45Z

Using the diginc/pi-hole-multiarch:v3.2.1_debian_armhf build, my container is restarting approximately every 20 seconds.

The mapped volumes are created but are empty.

Any ideas?

Docker log:

[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing...
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.

diginc · 2018-01-19T14:54:37Z

Try adding the environment variable PH_VERBOSE=1 to your container start. It should turn on debugging for some of the startup scripts.

diginc · 2018-01-25T16:43:41Z

Does this look anything like #217 ?

diginc · 2018-01-27T06:28:57Z

New *_dev tags are out for multiarch with #211 changes

https://hub.docker.com/r/diginc/pi-hole-multiarch/tags/

muddlethrough · 2018-01-28T12:21:34Z

Hi @diginc,

Apologies for the delay in getting back to you. I am not able to test at the moment due to being on the road. Will give it a test report back once I get back.

rspierz · 2018-02-03T02:27:28Z

I'm having the same issue with an RPiB on the newest dev image.

# docker logs pihole 
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.

diginc · 2018-02-05T14:54:48Z

set a docker run environment variable to PH_VERBOSE=1 and it should show you why 20-start.sh is existing with a weird return code....

rspierz · 2018-02-05T15:58:20Z

Here is my docker run:
docker run --net=host -e PH_VERBOSE=1 -e WEBPASSWORD="****" -e ServerIP="***" --restart=always --name pihole -d diginc/pi-hole-multiarch:debian_armhf_dev.

This is what I get in docker logs pihole:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

DXPetti · 2018-02-06T09:50:58Z

Getting the same error on my rpi0 from a fresh pull of both diginc/pi-hole-multiarch:debian_armhf and debian_armhf_dev

[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.

Adding the environment variable doesn't seem to give any extra detail when querying the container log.

This issue isn't present with the same docker run commands when using the old diginc/pi-hole:arm_v3.1 tag

Docker version below:

docker version
Client:
 Version:      17.04.0-ce
 API version:  1.28
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Mon Apr  3 18:22:23 2017
 OS/Arch:      linux/arm

Server:
 Version:      17.04.0-ce
 API version:  1.28 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Mon Apr  3 18:22:23 2017
 OS/Arch:      linux/arm
 Experimental: false

Run commands:

docker run -d \
    --name pihole \
    -p 53:53/tcp -p 53:53/udp -p 80:80 \
    -v "${DOCKER_CONFIGS}/pihole/:/etc/pihole/" \
    -v "${DOCKER_CONFIGS}/dnsmasq.d/:/etc/dnsmasq.d/" \
    -e ServerIP="${IP:-$(ip route get 8.8.8.8 | awk '{ print $NF; exit }')}" \
    -e ServerIPv6="${IPv6:-$(ip -6 route get 2001:4860:4860::8888 | awk '{ print $10; exit }')}" \
    -e PH_VERBOSE=1 \
    --restart=always \
    diginc/pi-hole-multiarch:debian_armhf_dev

docker logs pihole 2> /dev/null | grep 'password:'

glitchcrab · 2018-02-11T22:47:36Z

Just to add to this, I ran with PH_VERBOSE=1 and got the following:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Hardware is a Raspberry Pi Model B Rev 2 and I'm trying v3.2.1_debian_armhf

Kevin-De-Koninck · 2018-03-11T20:19:59Z

I got the exact same problem. Is there any progress on this?
I'm running it on Linux raspberrypi 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux

xac1d · 2018-03-18T21:39:16Z

same here. any one find a fix?

diginc · 2018-03-19T18:19:40Z

It didn't click with me until I saw Armv6 in Kevin's comment. The images I'm able to build virtually in the cloud are limited to ARMv7+ / ARMHF unfortunately.

The ReadMe is a little misleading since the install docker step for raspberry Pi says

Install docker for your x86-64 system or ARMv6l/ARMv7 system using those links.

but the ARMHF image is not Armv6 compatible. Although docker installs on armv6 my image won't work on it because ARMHF != ARMV6.

I had previously brought up that there maybe some hope for the older armv6 architectures by using armel. That issue also has some more details about why I'm not shipping anything but armhf images, rather than repeat it all here I ask you look #116 over.

Another relevant pre RBI2B support comment

diginc · 2018-03-19T18:33:13Z

#244 will make the current support clearer in the readme, sorry for the confusion.
#245 is a reminder to myself or anyone else curious about getting an armv6 image building

bd12 · 2018-07-05T20:21:19Z

hey all,
I can reproduce the above problems with my raspberry pi 1 b.
@diginc: will this enhancement be (re-) considered?

fyi, that's my setup:

kernel and os :

$ uname -a
Linux raspi 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linux

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"

docker:

$ docker version
Client:
 Version:      18.05.0-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   f150324
 Built:        Wed May  9 22:24:36 2018
 OS/Arch:      linux/arm
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.05.0-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   f150324
  Built:        Wed May  9 22:20:37 2018
  OS/Arch:      linux/arm
  Experimental: false

docker logs after startup with '-e PH_VERBOSE=1'

$ docker logs -f pihole
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 20-start.sh: executing... 
[cont-init.d] 20-start.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

diginc · 2018-07-05T20:28:35Z

Please +1 / 👍 on this issue #245 - it's a successor / fix for this issue.

I've been working on making sure things are ready for the next big pi-hole release but that's nearly complete so I may have some time to work on the ARMEL/v6 version.

Docker Pi-hole does not support Raspberry Pi 1 Model B+ Ref.: pi-hole/docker-pi-hole#218 pi-hole/docker-pi-hole#245

PromoFaux · 2021-10-08T23:58:11Z

Closing due to being related about a very old tag. Copy pasting the below from elsewhere:

I've not yet been able to test this, but we added linux/arm/v6 support in the latest tag (2021.10 when we switched to using buildx for building mulitarch.. it's considered experimental, but hopefully it "just works"

diginc mentioned this issue Mar 19, 2018

Implement ARMEL based debian image for ARMv6 support #245

Closed

Kevin-De-Koninck mentioned this issue Mar 19, 2018

Unable to build from master branch #242

Closed

dt-rush mentioned this issue Sep 3, 2019

Does not work for rpizero klutchell/balena-pihole#17

Closed

JM1 added a commit to JM1/shelp that referenced this issue Jul 2, 2021

Drop Raspberry Pi 1 Model B+ from compatibility list

12f6a45

Docker Pi-hole does not support Raspberry Pi 1 Model B+ Ref.: pi-hole/docker-pi-hole#218 pi-hole/docker-pi-hole#245

PromoFaux closed this as completed Oct 8, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

pi-hole-multiarch:v3.2.1_debian_armhf not starting on Pi B #218

pi-hole-multiarch:v3.2.1_debian_armhf not starting on Pi B #218

muddlethrough commented Jan 15, 2018

diginc commented Jan 19, 2018

diginc commented Jan 25, 2018

diginc commented Jan 27, 2018

muddlethrough commented Jan 28, 2018

rspierz commented Feb 3, 2018

diginc commented Feb 5, 2018 •

edited

Loading

rspierz commented Feb 5, 2018

DXPetti commented Feb 6, 2018

glitchcrab commented Feb 11, 2018

Kevin-De-Koninck commented Mar 11, 2018 •

edited

Loading

xac1d commented Mar 18, 2018

diginc commented Mar 19, 2018 •

edited

Loading

diginc commented Mar 19, 2018

bd12 commented Jul 5, 2018

diginc commented Jul 5, 2018 •

edited

Loading

PromoFaux commented Oct 8, 2021

pi-hole-multiarch:v3.2.1_debian_armhf not starting on Pi B #218

pi-hole-multiarch:v3.2.1_debian_armhf not starting on Pi B #218

Comments

muddlethrough commented Jan 15, 2018

diginc commented Jan 19, 2018

diginc commented Jan 25, 2018

diginc commented Jan 27, 2018

muddlethrough commented Jan 28, 2018

rspierz commented Feb 3, 2018

diginc commented Feb 5, 2018 • edited Loading

rspierz commented Feb 5, 2018

DXPetti commented Feb 6, 2018

glitchcrab commented Feb 11, 2018

Kevin-De-Koninck commented Mar 11, 2018 • edited Loading

xac1d commented Mar 18, 2018

diginc commented Mar 19, 2018 • edited Loading

diginc commented Mar 19, 2018

bd12 commented Jul 5, 2018

diginc commented Jul 5, 2018 • edited Loading

PromoFaux commented Oct 8, 2021

diginc commented Feb 5, 2018 •

edited

Loading

Kevin-De-Koninck commented Mar 11, 2018 •

edited

Loading

diginc commented Mar 19, 2018 •

edited

Loading

diginc commented Jul 5, 2018 •

edited

Loading