Closed mslw closed 2 years ago
Possibly an indication that we need singularity v3. If so, this issues should be closed with some kind of documentation on that, somewhere.
From my POV there is little point in supporting singularity v2.
I can confirm that updating to Singularity 3 (specifically 3.10.0) solved this issue. All commands return with ok result.
ls -lh builder/envs
total 8.0K
-rw-r--r-- 1 mszczepanik mszczepanik 46 Jul 11 13:19 README.md
lrwxrwxrwx 1 mszczepanik mszczepanik 135 Jul 11 13:21 singularity-amd64.sif -> ../.git/annex/objects/V9/Kp/MD5E-s210337792--ba90081997dbd7244e08401e150a438f.sif/MD5E-s210337792--ba90081997dbd7244e08401e150a438f.sif
FTR I'm on Debian 11.4 (bullseye) and I installed Singularity from their GitHub release page (`singularity-ce_3.10.0-focal_amd64.deb)
Do you think that a short section "requirements" with a comment (saying that Singularity 3 is required) in ReST docs and / or the README file would be enough?
Now superseded by an issue related to documentation.
I was running
The second command prompted for sudo password (*within run command and printed all the regular datalad run & singularity outputs, ending with:
The
singularity-amd64.sif
file ends up created, but untracked by DataLad. It's owned by root:I'm on Singularity 2.6.1-dist, DataLad 0.17 and git-annex 10.20220322-1
Full WTF output
``` # WTF ## configuration