Skip to content
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] cachedir mountOption conflict with the custom volume #1132

Open
zxh326 opened this issue Oct 9, 2024 · 0 comments
Open

[BUG] cachedir mountOption conflict with the custom volume #1132

zxh326 opened this issue Oct 9, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@zxh326
Copy link
Member

zxh326 commented Oct 9, 2024

What happened:

configmap

volumeMounts :
  - name: jfs-cache
    mountPath: /data/cache
volumes :
  - name: jfs-cache
    persistentVolumeClaim:
      claimName: jfs-cache-pvc

and with cachedir=/data/cache option to create mountpod

will cause mountpod creation failure

error

mountPath: Invalid Value: "/data/cache":  must be unique

The reason is we will create a hostpath volume for each cachedir option.

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):
  • Kubernetes version (e.g. kubectl version):
  • Object storage (cloud provider and region):
  • Metadata engine info (version, cloud provider managed or self maintained):
  • Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
  • Others:
@zxh326 zxh326 added the kind/bug Something isn't working label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant