-
Notifications
You must be signed in to change notification settings - Fork 64
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
Can't mount CSI volume in unprivileged container #226
Comments
What distro are you running this on and is SELinux set to enforcing? |
I am not sure if relevant, the the CSI Driver I am using is JuiceFS with extended attributes turned off. |
What is the |
@jdoss I am using 0.4.2 specifically because it worked with the JuiceFS driver I suppose a work around is to mount the volume in a sidecar in the alloc directory, but I worry about unforseen issues with doing something like that. I also tried to manually edit the Podman seccomp policy to allow the unallowed function call, but it failed. Perhaps it does the function call only when not running privileged? I will try running the JuiceFS mount with extended attributes enabled and see if that helps. Edit: Nope, no difference. |
Hi @p1u3o 👋 Apologies for the delay here, somehow this issue fell through the cracks of my GitHub notifications. Which task driver are you using to run the CSI plugin? Would you be able to share that job with us? |
I'm having an issue where when attempting to use a
volume_mount
andvolume
stanza as follows below, the volume can not be mounted.If I add
privileged = true
to the container config, the mount works, but I don't see this as wise in production.rpc error: code = Unknown desc = failed to start task, could not start container: cannot start container, status code: 500: {"cause":"operation not supported","message":"lsetxattr /opt/nomad/data/client/csi/node/juicefs0/per-alloc/34725522-7bb4-8d4a-6f06-0d7646902b75/mxp-swift/rw-file-system-multi-node-multi-writer: operation not supported","response":500}
The text was updated successfully, but these errors were encountered: