Traceback (most recent call last):
File "/usr/local/miniconda/bin/fmriprep", line 10, in <module>
sys.exit(main())
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/run.py", line 311, in main
opts = get_parser().parse_args()
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/run.py", line 284, in get_parser
latest = check_latest()
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/version.py", line 22, in check_latest
cachefile.parent.mkdir(parents=True, exist_ok=True)
File "/usr/local/miniconda/lib/python3.7/pathlib.py", line 1241, in mkdir
self._accessor.mkdir(self, mode)
OSError: [Errno 30] Read-only file system: '/home/fmriprep/.cache/fmriprep'
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='templateflow.s3.amazonaws.com', port=443): Max retries exceeded with url: /tpl-OASIS30ANTs/tpl-OASIS30ANTs_res-01_T1w.nii.gz (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x2aaacc203198>: Failed to establish a new connection: [Errno 110] Connection timed out'))
Can you attempt to download it with curl from the network that you are running the singularity container on to confirm you can reach it? If you can curl it outside of the singularity image but not from inside of it that might narrow the issue down. If the only place that url is not accessible is from inside the singularity container it might be worth trying to recreate the singularity image from docker manually: https://fmriprep.readthedocs.io/en/stable/installation.html#singularity-container
Ok, sorry, looks like the problem is our compute nodes don’t have internet access. That said, the 1.4.1 image did not attempt to download things from the internet; is there a reason for this change?
Looks like you can download the templates to a directory mounted in singularity and fmriprep will read an environment variable on where to look for the templates: