Closed justinmans closed 2 weeks ago
Container image "10.129.1.25:1603/prometheus/prometheuis:v2.26.0" already present on machine Created container prometheus Started container prometheus Container image "10.129.1.25:1603/prometheus/prometheuis-operator:v0.47.0" already present on machine Created container config-reloader Error: failed to start container "config-reloader": Error response from daemon: failed to create shim: OCI rcuntime create failed: container linux.go:380: starting container process caused: exec: "/bin/prometheus-config-reloader": stat/bin/prometheus-config-reloader: no such file or directsory: unknown
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
I'm having the exact same problem and have no clue
I encountered this problem when upgrading, and I don't know how to solve it
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
0.13 same
my k8s version is 1.28 my kube-prometheus version is 0.13
I can't find any logs about alertmanager describe pod is:
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
Any progress on this issue, I can see the reloader image has the bin/prometheus-config-reloader file but when it is deployed in a pod, it cannot find it.
Same issue as everyone else. I have no idea how to fix this and am constantly in a CrashLoopBackoff
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
This issue was closed because it has not had any activity in the last 120 days. Please reopen if you feel this is still valid.
k8sveriosn:1.20.1
kube-prometheus:0.8 kube-prometheus-release-0.8
我在安装的时候
发现promethues的资源对象提示缺少文件,但是我的镜像来自镜像仓库pull的 报错情况如下:
希望能够得到帮助,我需要提供什么