Add support for Fusion file system for Sarus containerised task

[pditommaso]

Context

The Fusion file system allows using S3-compatible object storage as the task work directory.

This feature requires mounting the Fusion driver in the container process via a Fuse device.

When using Docker or Podman this can be achieved using the following options

--device /dev/fuse --cap-add SYS_ADMIN 

See #3337 for details.

Goal

The goal of this feature is to allow the use of Fusion driver in containers run via the Sarus container engine.

[pditommaso]

When trying to run a Fusion enabled container with Sarus, the following error is reported

$ sarus run wave.seqera.io/wt/82f195fe9205/nextflow/rnaseq-nf:v1.1
2022-12-26_20:10:11 Mounting FusionFS v0.6.1-e6da3a5
8:10PM ERR main.go:111 > mount fail error="exec: \"/bin/fusermount\": stat /bin/fusermount: no such file or directory"

The documentation reports how to allow Sarus to access FUSE file system mounted in the host.

However, there's no mention of mounting FUSE file system in the container space. Wondering @Madeeks has any suggestions at this regard?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.