We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please take a look the screen, thank you.
No response
The text was updated successfully, but these errors were encountered:
Do you observe the same behavior with similar permissions on a non-NFS mountpoint? I'm wondering if this is NFS-specific.
Sorry, something went wrong.
Yes, maybe NFS-specific.
PS: runc runtime work for all above mount point
For NFS mounts, we set disable_file_handle_sharing mount option:
disable_file_handle_sharing
gvisor/runsc/cmd/gofer.go
Lines 744 to 750 in c238e15
So it may have something to do with that option, in which gofer filesystem uses gofer.specialFileFD for regular files.
gofer.specialFileFD
No branches or pull requests
Description
Please take a look the screen, thank you.
Steps to reproduce
No response
runsc version
docker version (if using docker)
uname
No response
kubectl (if using Kubernetes)
repo state (if built from source)
No response
runsc debug logs (if available)
The text was updated successfully, but these errors were encountered: