search

prometheus-community / ipmi_exporter

Remote IPMI exporter for Prometheus
MIT License
471 stars 133 forks source link

Bring back Docker images for various ARCHs #103

Closed bitfehler closed 7 months ago

bitfehler commented 2 years ago

See also #100

33Fraise33 commented 12 months ago

Hi,

Any update to this? automated testing and local debugging on new mac systems fails because of this.

bitfehler commented 12 months ago

It's complicated. All prometheus exporters build on a very opinionated build system that is supposed to handle all this. But this exporter does not fit the pattern. Specifically, for Docker containers, the build system defaults to a very minimal base container that does not contain an actual distribution. This is fine for most exporters, as they only require the Go executable to be added to that system. The ipmi-exporter however requires additional software (FreeIPMI), so we cannot build on the standard base image. That itself works (for x86_64), but the build system part then assumes a very specific naming scheme for the base containers for other architectures which is simply not a thing for any images other than the "standard" base image.

I have neither the resources nor the motivation to untangle all this at the moment, but any help is more than welcome. The only other exporter I am aware of that has the same problem is the smartctl exporter, and it, too, produces only x86_64 containers. I would assume they might be interested as well.