[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] job Singularity submission/forced image starts



On 2/20/2018 10:48 AM, Thomas Hartmann wrote:
Hi all,

I am somewhat struggling to get jobs to start natively in Singularity.

Neither hard-wiring jobs to start transparently in a given Singularity
image nor with the user-side enabled image selection, I have managed to
get an (interactive) test job to start in the container.
On the node, the job starts runs without complaints but ssh and its
children are always directly attached to condor_starter without being
wrapped by Singularity (judging from ps). So far I have not found
something in the logs giving a hint.

Maybe somebody has an idea, what I might have missed?


Hi Thomas,

The story here is interactive shell jobs (i.e. "condor_submit -i") is implemented via condor_ssh_to_job. Currently condor_ssh_to_job does not interoperate with jobs launched inside of Singularity containers, and thus "condor_submit -i" will not (yet) interoperate with containers either.

Allowing condor_ssh_to_job to work with both Docker and Singularity jobs is something we want to fix. In fact, for the upcoming HTCondor v8.7.7 (currently in beta testing), we did fix it for Docker universe jobs [1]. Now that we fixed it for Docker, next up is Singularity...

regards,
Todd

[1] Ticket for condor_ssh_to_job with Docker is at
  https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=6558,56