Skip to content
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

Handle extra process time needed for the first pull of a container #25

Open
jackscanlan opened this issue Aug 20, 2024 · 1 comment
Open
Labels
low priority Things to do eventually

Comments

@jackscanlan
Copy link
Collaborator

When using shifter as the container platform, pulling a container for the first time can take much longer than the requested time through SLURM. The check_max + task.attempt code in nextflow.config might help with this in some cases but not always.

Not sure of a good solution. One idea could be to pull all required containers at the start of the pipeline in a dedicated process, but while this might work for shifter, it might not work for other container platforms. It would also require a list of containers to be kept, which isn't a bad idea for software versions etc.

@jackscanlan jackscanlan added the low priority Things to do eventually label Aug 20, 2024
@jackscanlan
Copy link
Collaborator Author

Pipeline parameter to flag first-time runs could boost the time for each process by a set amount to help cover container pulling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority Things to do eventually
Projects
None yet
Development

No branches or pull requests

1 participant