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

Re: [HTCondor-users] Under what conditions, if any, is the initial directory of a Singularity job the scratch space?



I'm currently on 2.6.0 from EPEL, but it appears that since the last time I checked, the 3.2.1 version has become available on the corporate mirror site.

The new version doesn't drop me in the root directory, but rather in my bound home directory. But not the scratch directory.


Michael V. Pelletier
Information Technology
Digital Transformation & Innovation
Integrated Defense Systems
Raytheon Company

-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Bockelman, Brian
Sent: Tuesday, June 18, 2019 11:36 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [External] Re: [HTCondor-users] Under what conditions, if any, is the initial directory of a Singularity job the scratch space?

Hi Michael,

The setting of the initial working directory could be a version-dependent issue.  What version of Singularity are you utilizing?

Brian

> On Jun 18, 2019, at 12:57 PM, Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote:
> 
> I'm making my early forays into the Singularity world, and while I see that the execute directory is bound into the container by Condor, and TMPDIR and _CONDOR_SCRATCH_DIR are set, I'm finding in my tests that the initial directory of the container is not set to that directory, and I haven't been able to suss out a combination of options in the submit description that will put it there. I wind up either in root or my bound home directory.
> 
> I've seen an example of the server-side config adding a Singularity binding of "$(EXECUTE):/condor" so that we have a priori knowledge of the scratch location, but is there a way to avoid this workaround?
> 
> Michael V. Pelletier
> Information Technology
> Digital Transformation & Innovation
> Integrated Defense Systems
> Raytheon Company
> 
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/