Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SPANK plugin does not honour custom container path's from workbench #27

Open
michaelmayer2 opened this issue Feb 12, 2024 · 0 comments
Open

SPANK plugin does not honour custom container path's from workbench #27

michaelmayer2 opened this issue Feb 12, 2024 · 0 comments
Assignees
@michaelmayer2
Labels
bug Something isn't working

Comments

@michaelmayer2
Copy link
Contributor

When using Singularity integration with Workbench and Launcher > 2.15.1, the plugin still insist on its default value for singularity container path that is prepended. As a consequence, any SLURM job launched in a singularity container is failing.
@michaelmayer2 michaelmayer2 added the bug Something isn't working label Feb 12, 2024
@michaelmayer2 michaelmayer2 self-assigned this Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelmayer2 michaelmayer2

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michaelmayer2