-
Notifications
You must be signed in to change notification settings - Fork 250
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
Dask container recipe #545
Conversation
This container contains scripts that we use in our nextflow dask workflow, which we intend to submit to nf-core. |
I made the change to chmod in a separate step |
software.version label not matching directory version name |
Could not find the defined biotools entry, please check its name on biotools |
I saw the failure "Found some errors: software.version label not matching directory version name" - I named the folder based on the dask version, python version and os version - should I include all these in the software.version label? The current software version label is only showing the dask version |
I updated the software.version label to reflect the dir name |
Could not find the defined biotools entry, please check its name on biotools |
No test-cmds.txt (test file) present, skipping tests |
Ok, you should just remove the extra.identifiers.biotools="dask" , since I don't think it exists in biotools ? |
No biotools label defined, please check if tool is not already defined in biotools (https://bio.tools) and add extra.identifiers.biotools label if it exists. If it is not defined, you can ignore this comment. |
No test-cmds.txt (test file) present, skipping tests |
Seems fine to me, merging. |
Submitting a Container
(If you're requesting for a new container, please check the procedure described here.
Check BioContainers' Dockerfile specifications
Checklist
Check BioContainers' Dockerfile metadata