We are using singularity and the docker container needs some minor changes to be usable:
At least for the longitudinal batch at runtime the standalone code will replace the content of the pseudo compiled ".m" file with the content of a ".txt" file with the same name. Since with singularity the content of the container is read-only, this will fail and we replace at build-time. In theory this should also prevent docker runs from creating tiny unnamed volumes.
The container content often belongs to root with singularity and the CAT12 mex folder needs executable bit set for groups and others.
I also added a minimal example for a singularity invocation in the README.
WIP, we still haven't verified a batch completely, but it's looking good so far.
We are using singularity and the docker container needs some minor changes to be usable:
At least for the longitudinal batch at runtime the standalone code will replace the content of the pseudo compiled ".m" file with the content of a ".txt" file with the same name. Since with singularity the content of the container is read-only, this will fail and we replace at build-time. In theory this should also prevent docker runs from creating tiny unnamed volumes.
The container content often belongs to
root
with singularity and the CAT12 mex folder needs executable bit set for groups and others.I also added a minimal example for a singularity invocation in the README.
WIP, we still haven't verified a batch completely, but it's looking good so far.