A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

A new request to upload a container to <http://quay.io|quay.io> has been made!

• *Container URL:* <http://wave.seqera.io/wt/31a6e5f54e99/wave/build:b9dbc80cb5dd84ee|wave.seqera.io/wt/31a6e5f54e99/wave/build:b9dbc80cb5dd84ee>
• *Why is this needed?:* This is the universc container.
<https://github.com/nf-core/modules/pull/12955>

I would like to push the docker as well as the converted singularity image (to avoid OCI conversion).

I tried `wave -i <http://wave.seqera.io/wt/31a6e5f54e99/wave/build:b9dbc80cb5dd84ee|wave.seqera.io/wt/31a6e5f54e99/wave/build:b9dbc80cb5dd84ee> --singularity --freeze --build-repository <http://quay.io/nf-core/universc|quay.io/nf-core/universc> --tower-token=$TOWER_ACCESS_TOKEN` but this result in a failed container build/
• *Confirmation:*
    ◦ This can't be done through the usual Bioconda
Note: only containers with a stable version will be accepted (ie. not `latest`)

Core team will add this container to <http://quay.io|quay.io>. Please react to the message with :white_check_mark: when this is done.
[This process is not automated]

submitter: <@U03UCQH8FN2>

I would like to leave this one to <@UE4L64T4G> (or someone is familiar with the story) - I don't fully understand the history behind the licensing and what we are/are not allowed to do... and Phil flagged this on the module PR

We've just pushed before to our <http://quay.io|quay.io> - I'd prefer not to use wave if possible 

Yeah I think so. You were discussing it in the module PR linked above

This is indeed the container obtained from the latest dockerfile of the PR.
I created it through wave and was wondering if I should also create the singularity sif and store it on the <http://quay.io|quay.io>.
The test are now passing without the conversion, so I'm not sure it's necessary.

Yeah I'd prefer you just do it manually locally and push both to <http://quay.io|quay.io>

<@UQZG2UCF3> is advocating to push to seqera containers instead
I did in the past push to <http://quay.io/nf-core|quay.io/nf-core> but never to seqera containers through wave cli.
How can this be done ?

no strong feelings there. just thought we might be able to have  everything on seqera, but if phil prefers <http://quay.io|quay.io> i am fine with that

As the agreement was with nf-core, so would prefer to keep everything within that boundary

This should now be available through <http://quay.io|quay.io>
Should I try to fix the critical vulnerabilities ?