Re:Open-sourcing gVisor, a sandboxed container runtime
by zzzcpan on Wednesday May 02, 2018 @09:58AM
(#16976901)
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.
[ Parent
| on HN ]
Re:Open-sourcing gVisor, a sandboxed container runtime
by hugelgupf on Wednesday May 02, 2018 @01:23PM
(#16979126)
You 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.)
Re:Open-sourcing gVisor, a sandboxed container runtime
by beagle3 on Wednesday May 02, 2018 @11:20AM
(#16977736)
This 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
Re:Open-sourcing gVisor, a sandboxed container runtime
by zzzcpan on Wednesday May 02, 2018 @11:47AM
(#16978078)
I'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/0c7d73b31ae5e7ba506866...