What do you think about Quay.io?

Question

I noticed it's used by more and more open source projects and those projects are now publishing exclusively on quay.ioPersonally I think this is creating unecessary fragmentation of the docker image repositories.Also since 3 months there is this warning on quay.io website (all pages): We are currently facing technical issues with support@quay.io email. In order to contact Quay.io customer support, please use the email support@coreos.com until further notice.Really a tech company not being able to fix an email address for several months is quite concerning.Why do people consider using Quay.io?

EdwardDiego · Accepted Answer

I strongly suspect that a lot of those FOSS projects are backed by Red Hat, hence why they're using Quay, it's also Red Hat.
If they're not, I'm guessing there's favourable terms for FOSS projects, RH's entire business model is open source that they'll sell you support for.
And I fully agree that that banner is a terrible look.

xvello · Answer

Docker Hub's introduction of pull rate limits in 2020 created significant disruption for companies and big projects, and left a sour taste in a lot of people's mouth. I am not saying that they shouldn't have done it (bandwidth is not free of course), but I'm weary of what user-hostile move they will pull next.
As the maintainer of an open-source project that will publish container images, I am evaluating quay.io vs github packages, as both offer free storage and bandwidth for public projects. Docker has a process for open-source projects to apply and get rate-limits lifted, but why should I bother with it?
My last interaction with Quay was a couple of years ago (so a product might have evolved in the bad direction since), but at the time the publisher UX was pretty good, and the security scanning relevant.