DOC: Add Apptainer warning to Singularity docs #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhlegarreta
approved these changes
Jan 27, 2025
oesteban
changed the title
oesteban
reviewed
Jan 28, 2025
code review from Oscar Co-authored-by: Oscar Esteban <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a brief discussion at one of the monthly roundup meetings about Singularity vs. Apptainer. In our MRIQC protocol paper, we refer to it as Apptainer and link out to this documentation, so at minimum, I think we need to flag that anywhere in this documentation where you use
singularity, you can substituteapptainer. @jhlegarreta mentioned that the reality of the situation is not so straightforward as "Singularity was renamed to Apptainer", but that does seem to be the most succinct way to explain it without getting into the behind the scenes business details.@oesteban