-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] MountVolume.SetUp failed in GKE #222
Comments
Can you run You can use the follow command to check the node info.
|
Does GKE's kubelet has authority to create directory in k8s node? |
It looks like GKE node's root file system is read only. Does alluxio-mnt has to be in root / ? |
I've fixed it in #223. And please delete the existing chart and install with the chart: https://github.com/fluid-cloudnative/fluid/blob/fb123c104c4e0d8707260fcbb2b6de32f868054a/charts/fluid/fluid/values.yaml |
And please follow the updated guide: https://github.com/fluid-cloudnative/fluid/blob/master/docs/zh/samples/accelerate_data_accessing.md And notice:
|
What is your environment(Kubernetes version, Fluid version, etc.)
Kubernetes: 1.15
Fluid: 0.3.0
Helm: v3
Describe the bug
Followed instructions at here
Trying to install fluid with Helm3 on GKE. Found that PODS in fluid-system stuck in 'container creating' status. Only controller-manager pod runs well. Here is the log:
kubectl describe pod/csi-nodeplugin-fluid-6dsff -n fluid-system MountVolume.SetUp failed for volume "fluid-src-dir" : mkdir /alluxio-mnt: read-only file system
After changing the csi-nodeplugin-fluid daemonset.yaml by specifying the MountVolume as readOnly: False,
still not working.
What you expect to happen:
Fluid can be deployed on GKE
How to reproduce it
Helm install fluid fluid/
Additional Information
The text was updated successfully, but these errors were encountered: