Closed jdkent closed 6 years ago
This seems more like a nipype issue. Different mount outputs should've been handled more robustly.
It seemed to only happen on the centos 7 distribution with singularity, it worked fine with my local ubuntu computer on both docker and singularity. It appears to be a very niche error, but agreed, nipype could handle warnings better. Made a pull request working around that error to move forward here.
Setup:
Singularity container on CENTOS 7 server as the entry to a HPC cluster.
Behavior:
The error is coming from the
mount
commandExample
While the input expected is just
singularity on / type rootfs (rw)
: see nipype code