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

nf-core

in wave cli, how can i specify seqera containers as the `--build-repo`? <@UE4L64T4G>

<https://docs.seqera.io/wave/cli/use-cases#build-a-singularity-container>

for context i am trying to build from a dockerfile

`wave --containerfile  modules/nf-core/bcl2fastq/Dockerfile --context modules/nf-core/bcl2fastq --platform linux/amd64 --freeze -o yaml --log-level DEBUG --await` results in
```containerFile='IyBEb2NrZXJmaWxlIHRvIGNyZWF0ZSBjb250YWluZXIgd2l0aCBiY2wyZmFzdHEKIyBQdXNoIHRvIG5mY29yZS9iY2wyZmFzdHE6PFZFUj4KCkZST00gZGViaWFuOmJ1bGxzZXllLXNsaW0KTEFCRUwgYXV0aG9ycz0iTWF0dGhpYXMgRGUgU21ldCA8bWF0dGhpYXMuZGVzbWV0QHVnZW50LmJlPiIgXAogICAgZGVzY3JpcHRpb249IkRvY2tlciBpbWFnZSBjb250YWluaW5nIGJjbDJmYXN0cSIKIyBEaXNjbGFpbWVyOiB0aGlzIGNvbnRhaW5lciBpcyBub3QgcHJvdmlkZWQgbm9yIHN1cHBvcnRlZCBieSBJbGx1bWluYQojICdwcycgY29tbWFuZCBpcyBuZWVkZWQgYnkgc29tZSBuZXh0ZmxvdyBleGVjdXRpb25zIHRvIGNvbGxlY3Qgc3lzdGVtIHN0YXRzCiMgSW5zdGFsbCBwcm9jcHMgYW5kIGNsZWFuIGFwdCBjYWNoZQpSVU4gYXB0LWdldCB1cGRhdGUgXAogICAgJiYgYXB0LWdldCBpbnN0YWxsIC15IFwKICAgIHByb2NwcyBcCiAgICAmJiBhcHQtZ2V0IGNsZWFuIC15ICYmIHJtIC1yZiAvdmFyL2xpYi9hcHQvbGlzdHMvKgojIExpbmsgaG9zdG5hbWUgY21kIHRvIGZpeCBoYXJkY29kZWQgcGF0aApSVU4gbG4gLXMgL2Jpbi9ob3N0bmFtZSAvdXNyL2Jpbi9ob3N0bmFtZQoKIyBBZGQgZXhlY3V0YWJsZSB0byBpbWFnZQpDT1BZIGJjbDJmYXN0cSAvdXNyL2xvY2FsL2Jpbi9iY2wyZmFzdHEKCiMgQWRkIGV4dGVybmFsIGxpYnMgdG8gaW1hZ2UKQ09QWSBjc3MgL3Vzci9sb2NhbC9zaGFyZS9jc3MKQ09QWSB4c2wgL3Vzci9sb2NhbC9zaGFyZS94c2wKCiMgU2V0IHBlcm1pc3Npb24KUlVOIGNobW9kICt4IC91c3IvbG9jYWwvYmluL2JjbDJmYXN0cSAmJiBjaG1vZCAtUiArclggL3Vzci9sb2NhbC9zaGFyZS9jc3MgJiYgY2htb2QgLVIgK3JYIC91c3IvbG9jYWwvc2hhcmUveHNsCg==', containerConfig=null, condaFile='null', containerPlatform='linux/amd64', buildRepository='null', cacheRepository='null', timestamp='2026-02-16T16:55:23.422430+01:00', fingerprint='null', freeze=true, buildContext=ContainerLayer[location=data:H4sIAAAAAAAA/+19a3fb...; tarDigest=sha256:dd8f0ea9f51747c109e7644ef17e0dd89787497fb1e206677b07664776fc0365; gzipDigest=sha256:5b84680a2f677adc2abd2d10f7e3da2758f9c9f93b1c5d1390bb6c5a62089376; gzipSize=9927], type=null, dryRun=false, workflowId=null, containerIncludes=null, packages=null, nameStrategy=null, mirror=false, scanMode=null, scanLevels=null, buildCompression=null, buildTemplate=null}
15:55:23.554 [main] DEBUG io.seqera.wave.cli.Client - Wave response: statusCode=400; body={"message":"Attribute `buildRepository` must be specified when using freeze mode [1]"}
Wave invalid response: [400] {"message":"Attribute `buildRepository` must be specified when using freeze mode [1]"}```

Can't push to Seqera Containers with a custom Dockerfile

So that people can't use Seqera Containers as a free version of Dropbox

so should we push them to quay or not touch modules with dockerfile with any of our container commands?

I think we said in The Blog Post that we'd continue using <http://quay.io|quay.io> for these

But open to suggestions if you think that there's a better way

We did also say years ago that we could look into lifting this restriction for Seqera Containers for specific users, eg. nf-core