You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Soma-workflow servers can run inside a container (singularity, docker). However if it runs using a local scheduler, it cannot use an installed DRMS on the server submitting machine, because it cannot link with the host libdrmaa, nor use host-side commands such as qsub or qstat.
It might be possible to get out of the container for commands such as qsub or qstat, using tricks such as "ssh localhost qsub something" but it's not very nice. And I have no solution for DRMAA.
The text was updated successfully, but these errors were encountered:
1855844 allows the PBSpro scheduler to use qsub and qstat commands on the host (as long as ssh localhost works and allows to get outside of the container), so this DRMS should work in a container.
I don't see a convenient / robust solution for DRMAA inside a container. Maybe mounting the libdrmaa could work in some cases but it would depend on the system (just like singularity or docker use nvidia drivers).
Soma-workflow servers can run inside a container (singularity, docker). However if it runs using a local scheduler, it cannot use an installed DRMS on the server submitting machine, because it cannot link with the host libdrmaa, nor use host-side commands such as qsub or qstat.
It might be possible to get out of the container for commands such as qsub or qstat, using tricks such as "ssh localhost qsub something" but it's not very nice. And I have no solution for DRMAA.
The text was updated successfully, but these errors were encountered: