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
I've installed kepler in one of our k8s clusters using the chart provided in the "Kepler Deploy using Helm Chart" section from the official doc(https://sustainable-computing.io/installation/kepler-helm/).
No custom values file was needed, so I just used the basic helm installation.
After the daemonset is configured the two pods that are created in the kepler namespace are stuck in RunContainerError/CrashLoopBackOff with the following error:
Error: failed to create containerd task: failed to create shim task: Others("other error: container_linux.go:330: starting container process caused \"process_linux.go:381: container init caused \\\"rootfs_linux.go:61: mounting \\\\\\\"/proc\\\\\\\" to rootfs \\\\\\\"/run/containerd/io.containerd.runtime.v2.task/k8s.io/kepler-exporter/rootfs\\\\\\\" at \\\\\\\"/proc\\\\\\\" caused \\\\\\\"\\\\\\\\\\\\\\\"/run/containerd/io.containerd.runtime.v2.task/k8s.io/kepler-exporter/rootfs/proc\\\\\\\\\\\\\\\" cannot be mounted because it is located inside \\\\\\\\\\\\\\\"/proc\\\\\\\\\\\\\\\"\\\\\\\"\\\"\""): unknown
I am unsure of the root cause of this error, might be the fact that we're using containerd as the runtime but this is the first time I'm encountering this issue.
What did you expect to happen?
Both the daemonset and the pods should be up and running with the basic helm install configuration.
How can we reproduce it (as minimally and precisely as possible)?
What happened?
I've installed kepler in one of our k8s clusters using the chart provided in the "Kepler Deploy using Helm Chart" section from the official doc(https://sustainable-computing.io/installation/kepler-helm/).
No custom values file was needed, so I just used the basic helm installation.
After the daemonset is configured the two pods that are created in the kepler namespace are stuck in RunContainerError/CrashLoopBackOff with the following error:
I am unsure of the root cause of this error, might be the fact that we're using containerd as the runtime but this is the first time I'm encountering this issue.
What did you expect to happen?
Both the daemonset and the pods should be up and running with the basic helm install configuration.
How can we reproduce it (as minimally and precisely as possible)?
Step 1: helm repo add kepler https://sustainable-computing-io.github.io/kepler-helm-chart
Step 2: helm repo update
Step 3: helm pull kepler/kepler --untar
Step 4: helm install kepler kepler/ -n kepler --create-namespace
Anything else we need to know?
No response
Kepler image tag
Kubernetes version
Cloud provider or bare metal
OS version
No response
Install tools
Kepler deployment config
For on kubernetes:
For standalone:
put your Kepler command argument here
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: