Feature #18960
Updated by Tom Clegg over 1 year ago
If the new config option (@Containers.UseBuiltinMountWhenReadOnly@, default false) is @true@ _and_ there will Want to be no writes able to the fuse use Go FUSE driver as drop-in replacement for read-only collection mount (e.g., singularity image cache, output or other writable collection mounts specified by the container), crunch-run should start a points. Go fuse process instead of arv-mount. The fuse FUSE driver should be started in a separate process via @"/proc/self/exe mount ..."@ or similar, compiled into the crunch-run binary so it works (and uses that no additional software needs to be installed on the same code version as crunch-run itself) without any extra compute worker image preparation. Document any new runtime dependencies (hopefully none -- arv-mount already requires libfuse). node. Any missing features, performance regressions, or user-observable differences (e.g., crunchstat) relative to When actually launching the arv-mount setup should be noted as follow-up issues, but should not be considered blockers. The goal here is FUSE driver, we probably want to make fork it possible (similar to enable keepstore) to isolate potential failures from the Go option, starting with dev clusters, and test/measure for such differences and prioritize them accordingly. main crunch-run process.