You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version used: docker pull ncabatoff/process-exporter
Even 0.3.1 and 0.3.2 are listed as prerelease on the github release page,
the latest tag on dockerhub is pointing to 0.3.2.
Unfortunately 0.3.x are broken.
reproduction:
root@schulung:~# docker run --rm -i ncabatoff/process-exporter:0.2.12
2018/08/10 11:01:17 Reading metrics from /proc for procnames: []
root@schulung:~# docker run --rm -i ncabatoff/process-exporter:0.3.1
standard_init_linux.go:178: exec user process caused "no such file or directory"
root@schulung:~# docker run --rm -i ncabatoff/process-exporter:0.3.2
standard_init_linux.go:178: exec user process caused "no such file or directory"
root@schulung:~# docker run --rm -i ncabatoff/process-exporter:latest
standard_init_linux.go:178: exec user process caused "no such file or directory"
The text was updated successfully, but these errors were encountered:
Thanks very much for the detailed and timely bug report. It's fixed in v0.3.6.
I've added a 'stable' tag to the images (currently pointing to v0.2.12) which I will manually move when I consider a release to be ready, until I find a better solution. I've also added more checks to prevent this kind of breakage from happening in future.
Version used: docker pull ncabatoff/process-exporter
Even 0.3.1 and 0.3.2 are listed as prerelease on the github release page,
the latest tag on dockerhub is pointing to 0.3.2.
Unfortunately 0.3.x are broken.
reproduction:
The text was updated successfully, but these errors were encountered: