-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set default singularity cache directory to $WORKDIR/.singularity
#33
Comments
$WORKDIR/.singularity
$WORKDIR/.singularity
$WORKDIR/.singularity
Fixed on the feat_singularity_cache_fix branch. Alexei testing it out. |
did not fix the issue according to Alexei... I am not sure whye.. asking Kelly to test. @kelly-sovacool can you run these module load ccbrpipeliner
/gpfs/gsfs10/users/CCBR_Pipeliner/Pipelines/ASPEN/feat_singularity_cache_fix/bin/aspen --help
/gpfs/gsfs10/users/CCBR_Pipeliner/Pipelines/ASPEN/feat_singularity_cache_fix/bin/aspen -m=init -w=/data/CCBR/some/path
/gpfs/gsfs10/users/CCBR_Pipeliner/Pipelines/ASPEN/feat_singularity_cache_fix/bin/aspen -m=dryrun -w=/data/CCBR/some/path
/gpfs/gsfs10/users/CCBR_Pipeliner/Pipelines/ASPEN/feat_singularity_cache_fix/bin/aspen -m=run -w=/data/CCBR/some/path This should pull the dockers in |
/gpfs/gsfs10/users/CCBR_Pipeliner/Pipelines/ASPEN/feat_singularity_cache_fix/bin/aspen -m=run -
w=/data/$USER/aspen_test_iss-33 The message says it is setting the path correctly:
However, it did not change my default singularity cache dir in the shell (which I have set in my bashrc): echo $SINGULARITY_CACHEDIR
I also noticed there isn't a statement to export the cache dir in the bash submission script |
Trying to implement this sort of complex feature makes me want to rewrite the CLI in Python so we can begin writing unit tests, like we have for RENEE. |
need to modify these lines Lines 768 to 772 in f17382b
|
similar to RENEE's behavior.
Otherwise, users will run out of space if their
SINGULARITY_CACHEDIR
env var is set to the default in~/.singularity
The text was updated successfully, but these errors were encountered: