[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?
- Date: Wed, 19 Jun 2019 03:36:06 +0000
- From: "Bockelman, Brian" <BBockelman@xxxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Under what conditions, if any, is the initial directory of a Singularity job the scratch space?
The setting of the initial working directory could be a version-dependent issue. What version of Singularity are you utilizing?
> 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
> The archives can be found at: