-
Notifications
You must be signed in to change notification settings - Fork 17
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
[QUESTION]: NFS based mountpoint inside PODs always defaults to root:root #1204
Comments
Hi @anandhg02 , |
Hello Adarsh, Yes I found this later from the Release Notes section. What I intend to says was, can this be documented in a proper location may be under CSI Driver > Features and also explain the workaround as well, just my suggestion. |
@anandhg02, this aligns with troubleshooting. Would it be helpful if this was added to the Troubleshooting section? https://dell.github.io/csm-docs/docs/csidriver/troubleshooting/powerscale/. |
Agree, yes it can be part of Troubleshooting. But as this issue (fsGroup not working as expected) is common for any NFS based provisioning the Resolution or Workaround can be added under other storage arrays as well like PowerStore, Unity XT. |
@anandhg02 I've created a pull request (dell/csm-docs#1063). Please have a look when you have a moment to see if this addresses things. Thank you. |
Thanks a lot @gallacher |
You're very welcome @anandhg02 |
NFS based mountpoint inside PODs always defaults to root:root, as fsGroup securityContext does not apply to NFS mounts. But POD needs non-root access. This looks to be a known issue for NFS and the workaround is to use initCointainer to use chown command to set the required owner:group . It would be helpful if a reference be added in the CSM documentation about this.
Reference:
Why does my app fail when a non-root user owns the NFS file storage mount path? | IBM Cloud Docs
The text was updated successfully, but these errors were encountered: