Skip to content

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

@michaelmayer2

Description

@michaelmayer2

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.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions