nextflow-io / nextflow-io/nextflow
Add support for Fusion file system for Sarus containerised task
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Sarus container engine implementation and review issue #3337 for the related container options. Verify how Fusion's /dev/fuse device and SYS_ADMIN capability should be exposed for Sarus tasks, then confirm that a Fusion-backed task runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100