-
Notifications
You must be signed in to change notification settings - Fork 46
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] Is SYS_ADMIN
/ --privileged
capabilities needed to run geesfes within docker / k8s?
#127
Comments
Yes, FUSE needs it either for geesefs itself or for the |
Thanks! I think it would be very useful to mention these requirements and workarounds in the README, given that now more and more workloads are run inside docker / k8s and often without the admin capabilities... |
Also, there exists a project https://github.com/sholtrop/ldpfuse which tried on building a LD_PRELOAD'able library which transforms a FUSE-based file system into a LD_PRELOAD-based one. For many cases (and certainly for commands like Then it could be a workaround for k8s/docker installs which do not allow for CSI plugin or user namespace stuff yet. |
https://github.com/jacobsa/fuse doesn't use a C library, it directly talks to the fuse kernel device. There's also another FUSE binding used for Windows version of geesefs, it is based on the FUSE C library indeed. But anyway LD_PRELOAD is a really ugly hack %) |
For that second version, I wonder if geesefs can provide as a library C interface representing a state of virtual FS and low-level syscall/libc/posix-like functions for working with it? (like the interface in ldpfuse) If so, a custom implementation of LD_PRELOAD bridge could be easily implemented by a user (or the functions could be used for working with s3 from the user's custom C code) |
Typically these are needed to run
sudo mount
, but are these needed for running mounting with geesefs?I also wonder if
--mount
docker's cmdline argument could be used for creating geesefs mounts at container launch time?Thanks!
The text was updated successfully, but these errors were encountered: