Prometheus Exporter broken in v0.9.1
Describe the bug When using v0.9.1 we are getting following error on the exporter container:
Warning Failed 10m (x3 over 10m) kubelet Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/exporter/prometheus_varnish_exporter": stat /exporter/prometheus_varnish_exporter: no such file or directory: unknown
To Reproduce Just pull image locally and run the prometheus exporter command:
$ docker run -it --rm --entrypoint "/bin/bash" quay.io/mittwald/kube-httpcache:v0.9.1 /exporter/prometheus_varnish_exporter
/bin/bash: /exporter/prometheus_varnish_exporter: No such file or directory
Expected behavior Error should not happen and does not happen in v0.9.0
Additional context the symlinked file is missing in the /exporter folder:
$ docker run -it --rm --entrypoint "ls" quay.io/mittwald/kube-httpcache:v0.9.1 -l /exporter/
total 24
-rw-r--r-- 1 1001 118 5464 Jul 15 12:55 CHANGELOG.md
-rw-r--r-- 1 1001 118 1078 Jul 15 12:55 LICENSE
-rw-r--r-- 1 1001 118 5705 Jul 15 12:55 README.md
lrwxrwxrwx 1 root root 84 Jul 15 13:12 prometheus_varnish_exporter -> /exporter/prometheus_varnish_exporter-v1.7.0.linux-amd64/prometheus_varnish_exporter
@leontappe as I said before, this is broken in x86 and arm, let me know if I can help testing an alpha to fix this
Hello! We found a similar problem when updating to EKS 1.33 The problem is in the simlink. Below is an example of how we quickly fixed it via extraContainers I used this file for the build, leaving only the exporter https://github.com/mittwald/kube-httpcache/blob/master/build/package/docker/Dockerfile
extraContainers:
- name: prometheus-varnish-exporter
image: "xxxxx.dkr.ecr.eu-west-1.amazonaws.com/varnish-exporter/exporter:1"
command:
- /exporter/prometheus_varnish_exporter
args:
- -no-exit
env:
- name: VSM_NOPID
value: "1"
ports:
- name: metrics
containerPort: 9131
protocol: TCP
volumeMounts:
- name: var
mountPath: /var/lib/varnish
Hello @leontappe, any ETA about this? We are stuck in 0.9.0 waiting for the fix, let me know if you need a test.
Same issue here. I can't upgrade
Confirmed, workaround by using v0.9.0. I made the version pinning configurable in my integration cdk8s chart https://github.com/bluedynamics/cdk8s-plone/pull/97 (it was overdue anyway).