<env id="SINGULARITY_CACHEDIR”>-/some/path/</env> in your destination, but that will not pull the image to container_image_cache_path (during job execution)
singularity exec reusing a shared cache. Potential downside is that you always get the latest build which might break as we now. Also there is a warning in the docs regarding parallel use of the cache ..
Yes and no. We influence our community a lot with our playbooks.
Please @bgruening @natefoo @hexylena let us know as soon as you reach an agreement regarding the chosen OS. We're about to upgrade the OS of our Galaxy servers and would like to know the community consensus about the OS's for Galaxy.
BTW, there seems to be an alternative for CentOS coming up: https://rockylinux.org/
sure, but we still don't know how far they will work for that and the future community engagement on that project. We look expectant at it.
/api/tools does not return all of these. CONVERTER_bam_to_qname_sorted_bam is not returned. api/tools/CONVERTER_bam_to_qname_sorted_bam/requirements does return the tool's requirements. Is there a method I could use to get all of the tools including those not returned by /api/tools?