kubesphere / kubesphere/website
node-exporter CrashLoopBackOff
- Dominant language
- SCSS
- Stars
- 97
- Forks
- 418
- PR merge metrics
- No merged PRs in 30d
Description
本地k8s 单节点安装部署 kubesphere过程中 ,其中 node-exporter 报错 CrashLoopBackOff 并不断重启,
具体错误如下:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 8m23s default-scheduler Successfully assigned kubesphere-monitoring-system/node-exporter-hgsmq to docker-desktop
Normal Pulled 8m23s kubelet Container image "kubesphere/kube-rbac-proxy:v0.4.1" already present on machine
Normal Created 8m23s kubelet Created container kube-rbac-proxy
Normal Started 8m22s kubelet Started container kube-rbac-proxy
Normal Pulled 6m54s (x5 over 8m23s) kubelet Container image "kubesphere/node-exporter:ks-v0.18.1" already present on machine
Normal Created 6m54s (x5 over 8m23s) kubelet Created container node-exporter
Warning Failed 6m54s (x5 over 8m23s) kubelet Error: failed to start container "node-exporter": Error response from daemon: path /sys is mounted on /sys but it is not a shared or slave mount
Warning BackOff 3m13s (x23 over 8m21s) kubelet Back-off restarting failed container

Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported node-exporter pod events and the single-node Docker Desktop Kubernetes setup; inspect the node-exporter deployment and mount configuration. No repository file, test, or requested change is identified, so first establish whether this belongs as website documentation or an upstream configuration fix, then verify the pod no longer enters CrashLoopBackOff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- infrastructure, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100