-
Notifications
You must be signed in to change notification settings - Fork 7
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
Singularity: No space left on device #46
Comments
This looks like an issue with the mounted volumes for singularity rather than a problem with fmriprep-rodents, since similar issues were found in other NiPreps tools (see nipreps/mriqc#850 (comment) and https://sylabs.io/guides/2.5/user-guide/troubleshooting.html) |
This looks like an issue with scikit-image downloading files we're not requesting. Are we pinning a specific version? I remember them fixing something like this a while back. |
Nope. In fact, I don't think it's listed as a dependency anywhere outside of this GitHub action:
Does that ring any bells? Otherwise, it might be a problem with one of the dependencies. I'll try to recreate with the latest singularity image. |
This is the relevant issue: scikit-image/scikit-image#6069 We need to pin scikit-image >= 0.19 in the docker container. |
Is there any workaround I could use in the meantime, for example to allow for some writable space that would prevent this error from happening? |
Okay, so I have been trying to work out how to change Edited to add that I have also tried to do this with NiRodents lately, but I am clearly missing something. |
Bind a writeable directory into the data directory that failed to be written to. |
The processing pipeline fails because of errors such as:
OSError: [Errno 28] No space left on device: '/opt/conda/lib/python3.8/site-packages/skimage/data/../data/brick.png' -> '/home/fmriprep/.cache/scikit-image/0.18.3/data/../data/brick.png'
I tried setting the workdir explicitly following nipreps/fmriprep#2120 and nipreps/fmriprep#1291 and the issue remains.
What version of fMRIPrep are you using?
Latest fmriprep-rodents from docker as of April 19th
What kind of installation are you using? Containers (Singularity, Docker), or "bare-metal"?
Singularity
What is the exact command-line you used?
Have you checked that your inputs are BIDS valid?
The validator checks out
Did fMRIPrep generate the visual report for this particular subject? If yes, could you share it?
No
Can you find some traces of the error reported in the visual report (at the bottom) or in crashfiles?
Are you reusing previously computed results (e.g., FreeSurfer, Anatomical derivatives, work directory of previous run)?
No
The text was updated successfully, but these errors were encountered: