Pull and build containers in PDC_TMP #25
Open
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
|
Hi, I am creating a folder for Hydroglyphus on Dardel, I will try with these modifications. |
|
This will only take effect when a new container is pulled. Unless you're adding a new process, you shouldn't see an effect as the containers will be in the shared cache already. |
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.
Containers are usually built in $HOME which has a small quota, and can result in pipelines failing.
This changes where the containers are pulled and built ( when converting from docker images ) to PDC_TMP which is private to the user, has no quota limit, and only remains there for 30 days.
The final container images are still copied to the
NXF_SINGULARITY_CACHEDIRafter they've been built so they're available to everyone.