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
We want to run some of the Toil interpreters for WDL and CWL with TES under Funnel. We run TES jobs by running Toil containers, which we then pass a command through to figure out what CWL/WDL command is necessary for a certain job, which will then invoke another container to run the actual job. We do this to support reading/writing files that the underlying TES implementation cannot handle and because it simplifies things for us. For the nested container, we normally try to run it with Singularity, but Singularity needs additional permissions to run within a Docker container when the host machine has seccomp, which is very common. We would like some sort of way to specify running the TES job with certain additional Docker permissions to allow Singularity to run.
For example, some of the Docker options that we need: docker run -it --security-opt seccomp=unconfined --security-opt systempaths=unconfined [container] ...
Running the container as privileged with CAP_SYS_ADMIN or --privileged also gets around this issue, but we think the least permissive option is the docker command above, or defining a limited seccomp profile.
The text was updated successfully, but these errors were encountered:
We want to run some of the Toil interpreters for WDL and CWL with TES under Funnel. We run TES jobs by running Toil containers, which we then pass a command through to figure out what CWL/WDL command is necessary for a certain job, which will then invoke another container to run the actual job. We do this to support reading/writing files that the underlying TES implementation cannot handle and because it simplifies things for us. For the nested container, we normally try to run it with Singularity, but Singularity needs additional permissions to run within a Docker container when the host machine has seccomp, which is very common. We would like some sort of way to specify running the TES job with certain additional Docker permissions to allow Singularity to run.
For example, some of the Docker options that we need:
docker run -it --security-opt seccomp=unconfined --security-opt systempaths=unconfined [container] ...
Running the container as privileged with
CAP_SYS_ADMIN
or--privileged
also gets around this issue, but we think the least permissive option is the docker command above, or defining a limited seccomp profile.The text was updated successfully, but these errors were encountered: