Ask HN: What do you think about Quay.io?
I noticed it's used by more and more open source projects and those projects are now publishing exclusively on quay.io
Personally 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?
4 comments
[ 4.5 ms ] story [ 22.5 ms ] threadIf 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.
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.