Quay.io Help/Support Page

Updated -

Support for Quay.io

Quay.io is a registry for storing and building container images as well as distributing other OCI artifacts. The service is free for those who want to set up their own public repositories and available for a fee, if you want to create private repositories. Support is provided for paid users within the SLAs of our Red Hat Online Terms of Services. Support for billing and account-related issues, as well as service issues related to the hosted platform is available to Quay.io customers across all pricing tiers.

Red Hat provides Quay.io customers also access to product documentation and customer portal knowledge base for guidance and usage of the Quay.io platform. Technical support is primarily available for functionality and availability of the hosted service.

For service related incidents that are not listed on the Quay.io Status page, inclusive of availability, functionality or performance issues, paying customers should raise a technical support ticket using either of the available channels below. A Service incident is defined as an unplanned interruption of service or reduction in quality of service, and impacts multiple users of the service.

For generic inquiries about Quay.io functionality, pricing or getting started using Quay.io please see the following sections below.

Getting started with Quay.io

Before you can use Quay.io, you need to get a Quay.io account:

  • Go to Quay.io Plans and Pricing to choose from Developer, Micro, Small, and Larger plans
  • Select to start a 30-day free trial for your selected account

To start using Quay.io, you can:

Getting Quay documentation

Official Red Hat Quay documentation provides you with the most complete set of Quay feature descriptions. Here's what you can do with Quay.io:

Getting answers (Quay.io FAQ)

This section provides answers to Frequently Asked Questions about Quay.io.

Accessing the Quay.io Service

  • I can’t access Quay.io. How do I know that the service is running?

    • Go to the Quay.io Status Page to see the status of each component
    • Select SUBSCRIBE TO UPDATES to get on-going notifications when Quay.io incidents are created, updated, or resolved.
    • Send an email to Red Hat Support or call technical support if the problem is not resolved and you have a supported Quay.io plan.
  • How do I use Quay with my servers and code?

    • Using Quay.io with your infrastructure is separated into two main actions: building containers and distributing them to your servers. You can configure Quay to automatically build containers of your code on each commit. Integrations with GitHub, Bitbucket, GitLab and self-hosted Git repositories are supported. Each built container is stored on Quay and is available to be pulled down onto your servers. To distribute your private containers onto your servers, Docker or rkt must be configured with the correct credentials. Quay has sophisticated access controls — organizations, teams, robot accounts, and more — to give you full control over which servers can pull down your containers. An API can be used to automate the creation and management of these credentials.
  • How is Quay optimized for a team environment?

    • Quay's permission model is designed for teams. Each new user can be assigned to one or more teams, with specific permissions. Robot accounts, used for automated deployments, can be managed per team as well. This system allows for each development team to manage their own credentials. Full logging and auditing is integrated into every part of the application and API. Quay helps you dig into every action for more details.

Understanding accounts & billing

  • Who should I contact with questions about billing and account setup?

  • What features does each Quay.io plan include?

    • Quay.io Developer plan includes five private repositories and unlimited public repos
    • Quay.io Micro plan includes 10 private repositories, unlimited public repos, and team-based permissions
    • Quay.io Small plan includes 20 private repositories, unlimited public repos, and team-based permissions
    • Quay.io Larger plans includes 50 private repositories, unlimited public repos, and team-based permissions
  • Can I change my plan?

    • You can change your plan at any time and your account will be pro-rated for the difference. For large organizations, Quay Enterprise offers unlimited users and repos.
  • Do you offer special plans for business or academic institutions?

    • Please reach out to the appropriate Red Hat sales organization for your location from our Contact page to discuss the details of your organization and intended usage.
  • Can I use Quay for free?

    • Yes! We offer unlimited storage and serving of public repositories. We strongly believe in the open source community and will do what we can to help!
  • How do I recover a forgotten username/password?

    • In the event that you lose or forget your password, you can initiate a password recovery to the email associated with your Quay.io account. Click the "Forgot Password" link on the Sign In screen.
  • How do I change my contact details?

    • Log into Quay.io, select your username from the upper-right corner of the page, and select Account Settings. You can see User Settings and Billing Information from your profile.

Troubleshooting Quay.io


I was looking to get a service account to quay.io the same way it is possible to get one for registry.redhat.io. Actually the information I was looking for is https://access.redhat.com/solutions/3533201 there is a public account available to pull images.

As of today the corresponding auth proxy hasn't been added to Quay.io yet. We plan to do so later this year but so far it's not needed since Quay.io doesn't contain public repos yes although it's used to distribute Red Hat Quay and Red Hat OpenShift content. The pull secret and corresponding OpenShift configuration required for Red Hat Quay images can be found in the article you mentioned. Probably starting with Quay 3.3 we will distribute the Quay images and operators the same way as for all other Red Hat products via registry.redhat.io which then requires the service account you mentioned.

I found a bug and way trying to report it. That information is missing

Is there a way to convert a private repository to a public repository in Quay? Please help

Got it... There was an option in the settings to make it public. I missed it.. did not scroll down.. Not sure why I did not get an easy hit in google world to fix that... maybe because it was obvious to all but me :-) .. Thanks

Looks like support@quay.io doesn't exist anymore and it's still used in some parts of this article

I am trying to get user information such as First and Last name from Quay API, https://docs.quay.io/api/swagger/. But it doesn't seem there is an API call that I can use from that list. Anyone can help me with this one? (I don't know where to post a question, if you can redirect me to the right place, much appreciate it). Thanks!

User information is considered private, there are no API requests that will provide you with that information nor do we expose it anywhere in the UI except for the currently logged in user.

Cannot login to quay.io . Once I'm logging with Red Hat SSO , I got a captcha image , then error message : Red Hat login error The e-mail address xxxxxxx@redhat.com is already associated with an existing Quay account. Please log in with your username and password and associate your Red Hat account to use it in the future. But there are no option for login with username.

Hi @Gellert, you can go to https://recovery.quay.io/ to login with username and password and attach your quay.io account with your Redhat account

Similar to what happened to Gellert Kis, I'm trying to log in using my Github account, which is the one associated with our repo but can't.

Hi @Jose, you can go to https://recovery.quay.io/ to login with username and password and attach your quay.io account with your Redhat account

Thank you. A colleague passed me this article that was very useful https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0017609

Once I logged in to recovery.quay.io I had to detach and then reattach again.

I don't know where to put this issue, so I try here, if I'm wrong please let me know where to put this.

I'm struggling to find a way to make the build process NOT using the git cache. Inside my Dockerfile a clone of the Git repository is created (https://github.com/mmul-it/kpa/blob/main/Dockerfile#L43 ), but the problem is that the most of the times the git clone command uses it's cache, which makes the generated container image not consistent.

I've tried every sort of mechanism, like using CACHEBUST (or CACHE_BUST) argument in the Dockerfile, or using a specific tag in the clone operation specifying --branch, but nothing seems to help.

Is there a secure way to avoid this?

Many thanks!

You could try support@quay.io

I'm looking for a way to reset my Docker CLI Password for quay.io, but I can't seem to find it. Does anyone know how this can be done?

EDIT: I figured it out.. The "Change password" option on quay.io is for the Docker CLI Password. I just assumed this was for changing the login to the web portal, but its not.

The web portal is connected to redhat.com single-sign on service. You can actually maintain a separate password for Docker/Podman CLI clients. In the current UI, you can find it by clicking on your profile name and icon in the upper right hand corner of the Quay.io IO and go to "Account Settings". There it is the first section called "Docker CLI password".