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
This means toil-wdl-runner (and maybe toil-cwl-runner) is unable to run inside a default Docker command, ie docker exec -it toil_image toil-wdl-runner... after a default docker run toil_image.
This is resulting in some issues with the TES plugin, and might have other implications for other batchsystem plugins who want to run the Toil container via their own docker command. (Though the main issue with TES is it wants to run the container as read only)
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1558
The text was updated successfully, but these errors were encountered:
We do some trickery with syscalls and whatnot to allow Singularity to run inside the container
toil/src/toil/provisioners/abstractProvisioner.py
Line 820 in 5d436d3
This means
toil-wdl-runner
(and maybetoil-cwl-runner
) is unable to run inside a default Docker command, iedocker exec -it toil_image toil-wdl-runner...
after a defaultdocker run toil_image
.This is resulting in some issues with the TES plugin, and might have other implications for other batchsystem plugins who want to run the Toil container via their own docker command. (Though the main issue with TES is it wants to run the container as read only)
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1558
The text was updated successfully, but these errors were encountered: