Quay.io is a container registry for storing containers, Helm charts, and other container-related content. 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. Quay.io also includes features for building and scanning images.
Whether you are storing, building and deploying your own container images on Quay.io or just pulling images from Quay.io, this help/support page will help you:
- Find the information you are looking for to use Quay.io
- Track down problems you have using Quay.io
- Find other channels for getting help with Quay.io
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:
- Sign in to Quay.io
- Search the Quay.io registry
- Create a new image repository or application repository
- Push and pull some images, as described in Getting Started with Quay.io
- Try other tasks from the Use Red Hat Quay guide
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:
- Create an image repository
- Create an application repository
- Work with image tags
- Set up a custom git trigger
- Set up image repository event notifications
- Build images from Dockerfiles
- Download squashed container images
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?
- Contact Red Hat Customer Service with questions about Quay.io 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 contact us at our support email address 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.
How do I get help if I have a problem? Before contacting support, do this:
- Check Red Hat Quay Documentation
- Check Quay Special Interest Group. The Quay Sig is a public forum to ask questions and discuss Quay.io issues without requiring a paid subscription.
- Search Red Hat Customer Portal or Red Hat Solution Engine for Quay issues. Many of the solutions require a Red Hat subscription.
Contacting Red Hat Support
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 access to product documentation and customer portal knowledgebase 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, 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.