-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Description
Describe the bug
Node exporter pod underlying container fails to startup. This is the error reported by the deamon:
Error: failed to start container "node-exporter": Error response from daemon: path / is mounted on / but it is not a shared or slave mount
This error is related to #325 and it appears to be caused by this pull request. I've create this issue as suggested by @monotek in #80 (comment) (it appears that the original reporter of this issue has not created a new issue).
Moreover, I've tried to change kube-prometheus-stack chart manually to revert the commit above and I am able to deploy the chart without any error.
I am using docker-desktop
(v2.5.0.1) on Windows 10 1909 and I have enabled Kubernetes cluster from it.
I'm not sure if this error is caused by docker-desktop
, in any case, if it does not happen in other type of clusters, I would suggest to make the mount rootfs mountPropagation configurable via the chart values (and maybe enable it by default if you think it should not be optional) to prevent this error.
Another (better) solution would be to mount / as shared, but I've not found a way to do it.
Version of Helm and Kubernetes:
Helm Version:
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"}
Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.1", GitCommit:"7879fc12a63337efff607952a323df90cdc7a335", GitTreeState:"clean", BuildDate:"2020-04-08T17:38:50Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Which chart: kube-prometheus-stack
Which version of the chart: 12.7.0
What happened: node-exporter pod fails to startup
What you expected to happen: node-exporter should not fail
How to reproduce it:
No additional change in values.yaml file to reproduce.
The helm command that you execute and failing/misfunctioning:
helm install prom-stack prometheus-community/kube-prometheus-stack --version v12.7.0 -n monitoring