Pull the MinIO image from Quay - #1463
Conversation
MinIO deleted the minio/minio repository from Docker Hub on 2026-09-12, so every pull now fails with "repository does not exist". This follows their wind-down of the open source Community Edition, which entered maintenance mode in December 2025 and was archived in April 2026. The same tag is still served from quay.io, which is where MinIO's own documentation now points, so pull the image from there instead.
✅ Deploy Preview for testcontainers-node ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. Summary by CodeRabbit
WalkthroughThe MinIO Dockerfile now pulls from Quay.io. The installation documentation now links to the matching Quay.io repository. The MinIO release tag remains unchanged. ChangesMinIO registry update
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit hops beside the quay Comment |
Problem
MinIO deleted the
minio/miniorepository from Docker Hub on 2026-09-12. Every pull now fails:This is the tail end of their wind-down of the open source Community Edition, which stopped publishing free images in October 2025, entered maintenance mode that December, and was archived read-only in April 2026. The deletion was not announced. It broke CI across the ecosystem the same morning, including Milvus, Presto and Camunda.
This is why the
Tests (minio, ...)jobs currently fail on every open PR.Fix
Pull the same pinned tag from
quay.io, which is where MinIO's own documentation now points, and update the registry link in the docs to match.Worth noting Quay is a frozen snapshot rather than a maintained channel. No new releases will land there. Whether to keep MinIO at all is a separate question, but this unblocks CI.
Verification
The minio module tests pass locally against the Quay image.