images newer than ekofr/pihole-exporter:0.0.9 not running on arm

[andrebeekhuis]

I´m running pihole-exporter in docker on a raspberry. While ekofr/pihole-exporter:0.0.9 is running just fine, i would like to udate to the latest version to use a custom pihole webinterface port. The latest image sadly does not run on arm (exec user process caused "exec format error")

[baer95]

#72 seems to be related/the same issue.

[andrebeekhuis]

I have to correct, ekofr/pihole-exporter:0.0.10 is also running fine on arm. :latest (0.0.11) still has problems.

[creimer808]

Hey andrebbekhus,
my 0.0.9 image isn't working for me, I get this issue

you think you can help me out?

and yeah only 0.0.9 and 0.0.10 run, but they don't work for me specifically, both of them give the issue above

[andrebeekhuis]

Hey andrebbekhus,
my 0.0.9 image isn't working for me, I get this issue

you think you can help me out?

and yeah only 0.0.9 and 0.0.10 run, but they don't work for me specifically, both of them give the issue above

Sorry, i cant help you with that without more informations.

[bgoerz]

Hey andrebbekhus,
my 0.0.9 image isn't working for me, I get this issue

you think you can help me out?

and yeah only 0.0.9 and 0.0.10 run, but they don't work for me specifically, both of them give the issue above

please provide your configuration to get some help

[bgoerz]

I have to correct, ekofr/pihole-exporter:0.0.10 is also running fine on arm. :latest (0.0.11) still has problems.

same for me

[baer95]

this: 714576a is the change made in release 0.0.11. It looks like there is no code/feature change, 'only' changes to the docker image tagging and build process. Until the reason is found why 0.0.11 is not working on arm, it is probably safe to just use 0.0.10 instead of latest.

[ivanarsenijevic]

Hello,
I am having the same issue with 0.0.11 running on Raspberri Pi 3B+ with Raspberry Pi OS 32-bit.
I tried pihole-exporter:arm container and "docker logs pihole-exporter" indicates a problem in starting up the binary daemon. My troubleshooting attempt shows that an x86_64 file is supplied in the containers for arm architecture (I can confirm that for "arm" only as I haven't used others).
Compiling the "arm" pihole-exporter from the latest sources and putting it in place of the one in Container resolved the issue for me.

See README at https://hub.docker.com/r/ivanarsenijevic/pihole-exporter for troubleshooting details.

The only thing I can suspect - could it be that the "ARG ARCH=amd64" in Dockerfile (line 3) in the source code repository may be somehow hard-coded?

Anyway, thank you for creating the pihole-exporter, I find it very useful :-)

[logopk]

Now I want to add my findings:

:0.0.11 is running fine on my pi 3b+. It's digest show the correct tagging (OS/ARCH linux/arm/v7). It's not updated automatically with golang image updates though).
:arm is not running with the above exec format error (OS/ARCH is linux/arm)

From my own efforts to build the image, setting GOARCH=arm should be sufficient when built on the pi.

calling docker build with

docker build --build-arg ARCH=arm --tag ekofr/pihole-exporter:arm .

or docker-compose build with

services:
 pihole-exporter:
    build:
      context: ./
      args:
        ARCH: arm
      dockerfile: Dockerfile
    image: ekofr/pihole-exporter:arm