Trying to debug a build about singularityhub.github.io

[baxpr]

Yep, that was it. Thanks very much for the extra eyes!

[baxpr]

...one thing I do know is that running this binary uncompresses about 220 MB of files into a new folder. That is why it needs to be run in the first place - to generate these files in the container initially, because they can't be generated at runtime because the container is read-only.

[baxpr]

One more thing, here is a very similar situation where the build worked fine with ~800 MB of files unpacked:
https://github.com/baxpr/cersuit
https://singularity-hub.org/collections/4797

[vsoch]

@baxpr thank you for the detailed links! I haven't used spm in maybe 10 years so I'm feeling out of my base here - it does seem like there is some issue with the binary. Is the run_spm12.sh script made an executable, is it using the right interpreter, and then is spm12 what you think it is (e.g., it's not a dump from GitHub LFS saying "Sorry over quota!" or something like that. I would do some sanity checks - so remove piping to dev null where spm or matlab are concerned, and then when you download a text file or similar, cat the content (and for any downloads maybe check the digest) to be sure you are dealing with what you think you are.

@yarikoptic have you used SPM or Matlab more recently so you might know some ideas?

[baxpr]

Oh for heaven's sake. That's exactly what it is. I had marked the spm12 binary for LFS along with the actual large file spm12.ctf, but failed to download it so the container must be getting the github pointer instead of the file. Let me fix that and see if the problem doesn't go away.

[vsoch]

Fingers crossed! 🤞