- [minikube-3378]: Volume mount causes minikube VM to become corrupted
kubectl describe pod your-nodeplugin-pod shows:
failed to start container "your-driver": Error response from daemon: linux mounts: Path /var/lib/kubelet/pods is mounted on / but it is not a shared mount
Your Docker host is not configured to allow shared mounts. Take a look at this page for instructions to enable them.
If you have a Kubernetes 1.9 cluster, not being able to list VolumeAttachment
and the following error are due to the lack of the
storage.k8s.io/v1alpha1=true runtime configuration:
$ kubectl logs csi-pod external-attacher ... I0306 16:34:50.976069 1 reflector.go:240] Listing and watching *v1alpha1.VolumeAttachment from github.com/kubernetes-csi/external-attacher/vendor/k8s.io/client-go/informers/factory.go:86 E0306 16:34:50.992034 1 reflector.go:205] github.com/kubernetes-csi/external-attacher/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1alpha1.VolumeAttachment: the server could not find the requested resource ...
Please see the Kubernetes 1.9 page.
The external components images are under active development. It can happen that they become incompatible with each other. If the issues above above have been ruled out, contact the sig-storage team and/or run the e2e test:
go run hack/e2e.go -- --provider=local --test --test_args="--ginkgo.focus=Feature:CSI"