The Docker image 'deepops/prometheus-slurm-exporter' is based on too old version of Ubuntu.

[jungyh0218]

It's been already known that the current version of prometheus-slurm-exporter image occurs issue due to the old Ubuntu version of the base image.
Issue 1307

vpenso's prometheus-slurm-exporter is not maintained actively now, but I checked it still works fine with the Ubuntu 22.04 version and Golang >=1.24.

Here's the Dockerfile I wrote. I think the current version of deepops/prometheus-slurm-exporter & docker.slurm-exporter.service file should be updated.

I also have a plan to make the pull request in timely manner.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Please update the issue or it will be closed in 7 days.

[dholt]

Following up on this stale-closed issue as part of the resumed DeepOps release cadence: fixed in #1365 (merged). The role no longer pulls the 2020-era deepops/prometheus-slurm-exporter:latest — it builds a pinned image locally from a bundled Dockerfile on an Ubuntu 24.04 base, which resolves the glibc incompatibility with modern hosts' Slurm binaries. Live validation also surfaced and fixed two more defects in the same path: the unit never mounted sshare (the exporter's fair-share collector crash-looped on it), and an upstream exporter bug where sinfo -O default field widths make node names of 20+ characters merge into the next column and panic the collector on every scrape. All three fixes were validated end-to-end on a GPU deployment (48 slurm_* series serving, zero restarts) and ship in the next release (26.09). Thanks for the report — the abandoned-image concern was exactly right.