Pull MinIO from Quay: minio/minio was deleted from Docker Hub - #1921
Merged
Merged
Conversation
(cherry picked from commit 1a7fe98)
`quay.io/minio/minio:latest` is byte-identical to RELEASE.2025-09-07T16-13-09Z (sha256:14cea493d9a3...) -- Quay's community tags stopped moving when MinIO went source-only, so `latest` is a frozen 2025 image wearing a misleading name. Pin it, as dandi-cli already did once in #898, so the next registry surprise is a deliberate bump rather than a silent one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AxQytU7QLTU3qDrUWCzBwn
yarikoptic-gitmate
added
the
patch
Claude
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1921 +/- ##
=======================================
Coverage 77.35% 77.35%
=======================================
Files 89 89
Lines 13325 13325
=======================================
Hits 10307 10307
Misses 3018 3018
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
yarikoptic
added
tests
yarikoptic
approved these changes
Sep 14, 2026
|
🚀 PR was released in |
asmacdo
added a commit
to asmacdo/dandi-archive
that referenced
this pull request
Sep 21, 2026
`minio/minio:latest` no longer pulls from Docker Hub (access denied), so a fresh `docker compose up` fails before any service starts. Use quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z, the same pin dandi-cli's test fixture took in dandi/dandi-cli#1921. That fixture is what the "Test Integration with dandi-cli" workflow here runs against, so the dev compose and the CLI integration tests now use the same MinIO image. Quay's `latest` currently resolves to the same digest as this tag. Co-Authored-By: Claude Code 2.1.278 / Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MinIO deleted the
minio/minioandminio/mcDocker Hub repositories in September 2026, so every Docker-backed test job onmastercurrently dies indocker compose pullwithpull access denied ... repository does not exist. This points the test stack at Quay, which still serves the archived community images, and pins the tag.First commit is cherry-picked from @AtomicGlance's work in #1915, where it took the full matrix from red to green; it is unrelated to that PR's feature and belongs on
masteron its own. Second commit pins the tag.Background, verification, and why the pin
Timeline. In October 2025 MinIO stopped publishing free pre-built binaries and container images for the community edition — source-only from then on, pre-built artifacts became an enterprise deliverable. The images stayed up, stale but pullable, for about eleven months. Then between 2026-09-09 and 2026-09-12 (measured window ~18:12–20:13 UTC on 2026-09-11) the Docker Hub repositories were removed outright:
This broke CI across the ecosystem at the same moment — Grafana Mimir, Milvus, DataHub, Plane and many others all landed the same Quay redirect that week.
Why pin. Quay still serves the archived images, but they are frozen: the last community push there was 2025-09-07, and the only 2026 tags are
*.hotfix.*builds from the paid stream. Soquay.io/minio/minio:latestis a 2025 image wearing a name that implies it tracks something. The registry confirms the two tags are the same manifest:Byte-identical, so the pin runs exactly the image the #1915 matrix already proved green. dandi-cli pinned this image once before in #898 and drifted back to
latest; given MinIO just deleted a namespace with no notice, an explicit tag makes the next registry surprise a deliberate bump rather than a silent one.Knock-on effects.
dandi/dandi-archive'sdocker-compose.ymlstill pinsminio/minio:latest, so the dev stack is broken there too — separate PR to follow. (Their CI workflows already moved tobitnamilegacy/minio:latestin Switch minio docker image used by CI dandi-archive#2541.)dandi/backups2dataladhas no MinIO image of its own — it importsdandi.tests.fixturesand runs this very compose file, which ships in the wheel viagraft dandi. Its CI is red for this reason and will need a dandi-cli release, not just this merge. Labeledpatchaccordingly rather thantests/internal.Not verified locally: no Docker daemon in this environment, so the stack was not brought up here. Resolution of both tags to the same digest was checked against the Quay API, and CI on #1915 exercised that digest across the full matrix.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AxQytU7QLTU3qDrUWCzBwn
Generated by Claude Code