Hosting single container on GitHub registry

[edmundmiller]

drugresponseeval/nextflow.config

Lines 9 to 10 in 3d00d07

	process.container = 'ghcr.io/daisybio/drevalpy:main'
	process.conda = 'env.yml'

I noticed this in this conversation #11 (comment)

Just wondering if GitHub registry has any container pull rate limits/fees? We can get that built with Seqera containers and host it there since there's already an env file.

[JudithBernett]

Hi @edmundmiller , thank you for spotting this. I'm sorry I overlooked your issue!

As far as I understand, there is no pull rate limit for public repositories (https://github.com/orgs/community/discussions/49671). However, I am open to building a Sequera container and also hosting it there :) Can I do this myself / with a Github action like I'm doing right now for the ghcr container (https://github.com/daisybio/drevalpy/blob/development/.github/workflows/publish-docker.yml)?

[edmundmiller]

All good!

I see two options:

1. You can use the wave-cli like we did here: https://github.com/nf-core/modules/blob/master/.github/workflows/wave.yml
2. Theoretically you could just run the pipeline with wave(--with-wave) in CI and set wave.freeze