You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Conda-forge and bioconda seem to use https://quay.io rather than docker hub, so we should check if it makes sense to host our images on both registries and what the restrictions for the individual registries are.
The text was updated successfully, but these errors were encountered:
I think we cannot do anything wrong with hosting images at multiple places, esp. when it might increase visibility for other communities. @jan-janssen , can you maybe tell why exactly conda-forge and bioconda prefer https://quay.io/? I'm just curious and have never heard of quay before.
When considering this, I just like to note that there are of course many more container registries out there, e.g. github packages. Github packages is actually a broader framework for hosting packages of a number of technologies . I'm mentioning this here mainly, because of it's nice integration of github actions. Also, packages will be shown right in the repository from which they are generated, which is quite nice.
jan-janssen
changed the title
Publish Docker Container on quay.io
[Infrastructure] Publish Docker Container on quay.io
Nov 5, 2023
Conda-forge and bioconda seem to use https://quay.io rather than docker hub, so we should check if it makes sense to host our images on both registries and what the restrictions for the individual registries are.
The text was updated successfully, but these errors were encountered: