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
IMO, containers should usually be configured via environment variables, so it seems like datalad containers-run should accept --env and --env-file and pass along to singularity.
Alternatively, we could also add a flag --singularity-vars "env-file=/home/here" or similar.
The text was updated successfully, but these errors were encountered:
yeah, might be useful to allow for custom env configuration for a container. In principle that can already be possible for people by tuning their fork of this dataset and changing invocations in .datalad/config accordingly. Before bothering to improve upon that we better gain specific use cases to address.
IMO, containers should usually be configured via environment variables, so it seems like
datalad containers-run
should accept--env
and--env-file
and pass along to singularity.Alternatively, we could also add a flag
--singularity-vars "env-file=/home/here"
or similar.The text was updated successfully, but these errors were encountered: