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
I followed similar steps on our AWS EKS cluster but while accessing mounted s3 directories getting permission denied error -
d????????? ? ? ? ? ? s3fs
mount's are working fine of S3fs daemonsets I have created. Issue is only on additional containers where I am adding the s3fs as volume
Let me know what additional information I can provide
The text was updated successfully, but these errors were encountered:
Upgrade to s3fs 1.89
e166766
This fixes several data corruption and crashing bugs that may have caused freegroup#6. Fixes freegroup#7. Changelog: https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.85 https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.86 https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.87 https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.88 https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.89
Could you test with the latest master? This upgrades s3fs to 1.89 which resolves several issues that could cause these symptoms.
Sorry, something went wrong.
No branches or pull requests
I followed similar steps on our AWS EKS cluster but while accessing mounted s3 directories getting permission denied error -
d????????? ? ? ? ? ? s3fs
mount's are working fine of S3fs daemonsets I have created. Issue is only on additional containers where I am adding the s3fs as volume
Let me know what additional information I can provide
The text was updated successfully, but these errors were encountered: