-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for custom fuse device plugin #4612
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Paolo Di Tommaso <[email protected]>
✅ Deploy Preview for nextflow-docs-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Wow, this is less than half an hour, wonderful! |
bentsherman
approved these changes
Jan 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just need to document the new option
Signed-off-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Feb 6, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Feb 6, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Feb 6, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Feb 12, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Feb 12, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Apr 3, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
nschan
pushed a commit
to nschan/nextflow
that referenced
this pull request
Apr 3, 2024
This commit allows customising the FUSE plugin device required by Fusion when using the Kubernetes executor. The FUSE plugin name can be specified by using the setting `k8s.fuseDevicePlugin` for example: ``` k8s.fuseDevicePlugin = ['my-plugin/fuse': 1] ``` Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Niklas Schandry <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Nextflow uses Fusion over K8s with unprivileged mode requires the use of the k8s-fuse-plugin to mount the FUSE device.
Other plugins are available which requires the use of a custom fuse device name to be specified in the K8s spec.
This PR adds the ability to specify a custom fuse device name via the nextflow config file. For example:
Solved #4611