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

Re: [HTCondor-users] Submit-specified Singularity bind paths?

Hi Michael,

This seems to work for additional user specified bind paths:

SINGULARITY_BIND_EXPR = ifThenElse(isUndefined(TARGET.SingularityBind), \
                      $(SINGULARITY_BIND_BASE), \
                      join(",", $(SINGULARITY_BIND_BASE), TARGET.SingularityBind))

where the submit file adds an optional new attribute SingularityBind e.g.

queue 1

Though there is probably a better of writing this configuration.



On Tue, 9 Oct 2018 at 05:40, Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote:
Is it possible for the job submission to specify a "SingularityBind" attribute to add paths to the SINGULARITY_BIND_EXPR, or is that solely under the control of the configuration files?

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:

Paul Hopkins
Computational Infrastructure Scientist
Cardiff University | Prifysgol Caerdydd
+44 (0) 29 225 10043