3 ms·
Is it possible to hook a custom filesystem implementation to this? So an app won't touch filesystem at all but still will be able to use some sort of virtual fi
by zzzcpan 9y ago
Is it possible to hook a custom filesystem implementation to this? So an app won't touch filesystem at all but still will be able to use some sort of virtual files.
- beagle3 9y agoThis has been possible and quite easy with FUSE (and overlayfs / mergerfs / mhdfs / aufs if you don't want to implement all the functionality yourself) for the last 8 years at least -- I've used mhddfs and fuse for exactly this on Ubuntu 10.04
- zzzcpan 9y agoI'm not interested in fuse here. Gvisor has fsgofer, which is a proxy of some kind to a filesystem, there is even ReadAt [1]. But it is light on details, I was curious how and to what extent it proxies filesystem API. [1] https://github.com/google/gvisor/blob/0c7d73b31ae5e7ba5068669306aefe5a7b559f92/runsc/fsgofer/fsgofer.go#L720 https://github.com/google/gvisor/blob/0c7d73b31ae5e7ba506866...
- hugelgupf 9y agoYou can implement a custom file system as a separate process (called Gofers) and have the sandbox connect to that. The custom file system has to adhere to the p9.File API (see pkg/p9/file.go) - the protocol is an extended version of 9P2000.L. (I work on gVisor.)