Sitelet https://github.com/testcontainers/testcontainers-node/pull/1463
Skip to content

Pull the MinIO image from Quay - #1463

Merged
cristianrgreco merged 1 commit into
mainfrom
minio-quay-registry
Sep 21, 2026
Merged

cristianrgreco merged 1 commit into
mainfrom
minio-quay-registry

Conversation

@cristianrgreco

Copy link
Copy Markdown
Collaborator

Problem

MinIO deleted the minio/minio repository from Docker Hub on 2026-09-12. Every pull now fails:

(HTTP code 404) unexpected - pull access denied for minio/minio,
repository does not exist or may require 'docker login'

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.

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.
@netlify

netlify Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for testcontainers-node ready!

Name Link
🔨 Latest commit e2a826f
🔍 Latest deploy log https://app.netlify.com/projects/testcontainers-node/deploys/6ab1518852006c0008f0bcae
😎 Deploy Preview https://deploy-preview-1463--testcontainers-node.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View blast radius →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 1152ff68-57ff-4f31-ad0b-082309ac9f30

📥 Commits

Reviewing files that changed from the base of the PR and between 99ff0a2 and e2a826f.

📒 Files selected for processing (2)
  • docs/modules/minio.md
  • packages/modules/minio/Dockerfile

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.


Summary by CodeRabbit

  • Updates
    • MinIO container images are now sourced from Quay.io while retaining the existing release tag.
    • Updated MinIO documentation to direct users to Quay.io when selecting an image.

Walkthrough

The MinIO Dockerfile now pulls from Quay.io. The installation documentation now links to the matching Quay.io repository. The MinIO release tag remains unchanged.

Changes

MinIO registry update

Layer / File(s) Summary
Update MinIO registry references
packages/modules/minio/Dockerfile, docs/modules/minio.md
The Dockerfile uses quay.io/minio/minio. The documentation links to the Quay.io repository. The MinIO release tag remains unchanged.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely states the main change: pulling the MinIO image from Quay instead of Docker Hub.
Description check ✅ Passed The description directly explains the Docker Hub failure, the Quay registry change, the documentation update, and the verification result.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

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.

❤️ Share

A rabbit hops beside the quay
MinIO follows a brighter way
The tag stays fixed and clear
The docs now point to where
Containers wait without delay

Comment @coderabbitai help to get the list of available commands.

@cristianrgreco cristianrgreco added the maintenance Improvements that do not change functionality label Sep 21, 2026
@cristianrgreco
cristianrgreco merged commit efd6599 into main Sep 21, 2026
17 checks passed
@cristianrgreco
cristianrgreco deleted the minio-quay-registry branch September 21, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Improvements that do not change functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant