-
Notifications
You must be signed in to change notification settings - Fork 58
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 (apptainer) instructions #529
Comments
This is the result of using |
Thanks for setting me straight! I agree that it might be nice to have this spelled out in the documentation for the luddites such as myself, but this might also be out of scope for qsiprep, so I'd also be sympathetic if this issue is closed with no further action taken. |
For reference, the documentation for this comes from here. This will definitely need an option for supporting apptainer though. |
For now, installs of apptainer alias singularity, but I don't know when that will phase out. |
@arokem you recently updated the Singularity/Apptainer documentation. Do you think this is good to close? |
I don't think that I properly addressed the |
We are using qsiprep on an HPC cluster that requires use of apptainer (i.e., singularity the next generation).
We found that when we run the singularity command as described here, we run into some issues. Basically, our issue was that we started off by converting the docker image into a singularity image and then tried to use the docker command, but there are subtle differences between how this is run in docker and how this should be run in apptainer. Maybe it would be good to document this difference? We believe it should be something like:
In contrast to the docker command, this command has an additional
qsiprep
between the name of the image and the names of the folders (which is not required in the docker image, as it has that as an entrypoint). We would've submitted a PR to fix this, but we don't exactly understand how this section of the documentation gets generated.CC: @teresamg, @mckenziephagen
The text was updated successfully, but these errors were encountered: