What happened:
After successfully deployed juicefs csi and create pvc, a demo pod mount the pvc failed, the mount pod error msg is:
'MountVolume.SetUp failed for volume "updatedb" : open /etc/updatedb.conf: read-only file system'
The file not exits on k8s worker node but can create it manually.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
JuiceFS CSI Driver version (which image tag did your CSI Driver use):
v0.25.2
Kubernetes version (e.g. kubectl version):
v1.28.11
Object storage (cloud provider and region):
Metadata engine info (version, cloud provider managed or self maintained):
redis
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
What happened: After successfully deployed juicefs csi and create pvc, a demo pod mount the pvc failed, the mount pod error msg is: 'MountVolume.SetUp failed for volume "updatedb" : open /etc/updatedb.conf: read-only file system' The file not exits on k8s worker node but can create it manually.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
JuiceFS CSI Driver version (which image tag did your CSI Driver use): v0.25.2
Kubernetes version (e.g.
kubectl version): v1.28.11Object storage (cloud provider and region):
Metadata engine info (version, cloud provider managed or self maintained): redis
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others: