mirror of
https://github.com/quay/quay.git
synced 2026-01-26 06:21:37 +03:00
bd587488c8
This fix resolves an issue where cached images required upstream registry availability to be pulled, defeating the purpose of the proxy cache feature. Problem: - The _update_manifest_for_tag() method always contacted the upstream registry via manifest_exists() HTTP HEAD request - When upstream registry was unavailable, pulls failed with 504 timeout - This occurred even when the manifest and blobs were fully cached Solution: - Add early return that serves from cache when: 1. Tag is not expired (still within TTL) 2. Manifest is not a placeholder (has full content) - Only contact upstream when tag expired or manifest incomplete - Reduces upstream traffic and improves availability Benefits: - Cached images work when upstream unavailable - Reduced upstream registry traffic - Lower latency for cached pulls - True proxy cache behavior (cache-first) Fixes: https://issues.redhat.com/browse/PROJQUAY-8440 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Project Quay
⚠️ The master branch may be in an unstable or even broken state during development.
Please use releases instead of the master branch in order to get stable software.
Project Quay builds, stores, and distributes your container images.
High-level features include:
- Docker Registry Protocol v2
- Docker Manifest Schema v2.1, v2.2
- OCI spec v1.1 support oci
- Authentication provided by LDAP, Keystone, OIDC, Google, and GitHub
- ACLs, team management, and auditability logs
- Geo-replicated storage provided by local filesystems, S3, GCS, Swift, Ceph and ODF
- Continuous Integration integrated with GitHub, Bitbucket, GitLab, and git
- Security Vulnerability Analysis via Clair
- Swagger-compliant HTTP API
Getting Started
- Explore a live instance of Project Quay hosted at Quay.io
- Watch talks given about Project Quay
- Review the documentation for Red Hat Quay
- Get up and running with our getting started guide for developing or deploying Quay
- Deploy on Kubernetes using the Quay Operator
Community
- Mailing List: quay-sig@googlegroups.com
- IRC: #quay on libera.chat
- Bug tracking: Red Hat JIRA
- Security Issues: security@redhat.com
- Community meetings held the first Wednesday of every month 11:00 AM EST: meeting link
License
Project Quay is under the Apache 2.0 license. See the LICENSE file for details.