-
Notifications
You must be signed in to change notification settings - Fork 740
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
"Local" nf-core modules without singularity container builds cause issues #1516
Comments
IIRC this is a product of Seqera Containers usage. @maxulysse was of the opinion that everything should be in quay.io, so mirrored SC containers there, leaving Singularity conversion to happen dynamically. |
Hey @maxulysse could you document why #1441 was necessary at the time? Just for reference in this conversation. Is it just because it made it easier to mirror everything if it was all in quay.io? Because |
So for me, there is 2 components here:
The mirroring to quay.io was done because it was preferable to have a single registry to simplify local mirroring. |
Ok. If https://nf-co.re/blog/2024/seqera-containers-part-2 is something that's actually happening I guess this isn't worth caring about. |
At a minimum, in the short term, I think we've agreed to revert the patches here which underly most of these issues. |
It seems there's been a number of nf-core modules that have been patched locally in nf-core, relating to specific container builds. I'm not sure why these have been made, but they seem to lack singularity builds which makes offline use harder, causes needless rebuild wait and an overall suboptimal experience.
These specific builds don't seem to have been fed-back to nf-core/modules, so I'm not sure if there's a plan for them.
The ones I've seen are
The text was updated successfully, but these errors were encountered: