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

Feature request: Singularity images for Dockerfile-based containers #14

Open
krokicki opened this issue Oct 19, 2023 · 0 comments
Open

Comments

@krokicki
Copy link

krokicki commented Oct 19, 2023

I recently added a couple of containers to BioContainers/containers: spark and stitching-spark. I used the Dockerfile route because I have no need to run Spark with Bioconda and because I'm not sure these would make sense to deploy into Bioconda.

My intention with these containers is to use them in Nextflow pipelines (e.g. lightsheetrecon) to create transient Spark clusters for large microscopy data processing.

The containers were successfully built and deployed to DockerHub:
https://hub.docker.com/r/biocontainers/stitching-spark
https://hub.docker.com/r/biocontainers/spark

However, they are not being converted to Singularity and made available on galaxyproject.org. My understanding based on the docs is this is intentional: it seems that BioConda images are pushed to quay.io and are then converted to Singularity, but Dockerfile-based images are pushed to DockerHub which is not scanned by this project.

I'm curious why this division exists and if it would it be possible to convert the Dockerfile-based images on DockerHub to Singularity as well?

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

No branches or pull requests

1 participant