fix: point MinIO template at its still-public registry path - #913
Merged
Merged
Conversation
quay.io/minio/minio (and Docker Hub's minio/minio) retired free anonymous pulls in Sept 2026, breaking every deploy of this template with a 401. quay.io/minio/aistor/minio is MinIO's replacement public path; also swaps the healthcheck off wget, which the new RHEL UBI-based image doesn't ship. Verified: pulled the new image, ran it with the template's exact command, and confirmed the new curl-based healthcheck reports healthy.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 27 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
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. Comment |
|
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
1 participant
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.
What
internal/catalog/templates_storage.go: the MinIO template'squay.io/minio/minio:RELEASE.2025-09-07T16-13-09Zimage is dead. Points it atquay.io/minio/aistor/minio:RELEASE.2026-09-19T17-05-25Z.hotfix.4ef74f03d6f2instead.wgettocurl -sf: the new image is RHEL UBI-based and doesn't ship wget.Why
Reported: deploying the MinIO template failed with
401 UNAUTHORIZEDpulling the pinned tag. Checked directly against the registry (anonymous token exchange):quay.io/minio/minioreturns 401 on every tag includinglatest, and Docker Hub'sminio/minioreturns "object not found". MinIO retired free/anonymous container distribution on both registries in September 2026 as a business decision pushing toward their commercial AIStor product, confirmed by a string of GitHub issues from the same week across unrelated projects. Not a bug in our pull path.The stale tag had already been flagged in a code comment ("Tag unverified: quay.io returns 401 anonymously...") from the original Coolify-catalog import, but shipped anyway.
Test plan
go build ./...,go test ./internal/catalog/...quay.io/minio/aistor/miniois anonymously pullable (registry token exchange, HEAD on manifest)docker pullthe exact new tagserver /data --console-address :9001command and the new healthcheck command directly; confirmed Docker reports the containerhealthyand the console (:9001) responds 200What this does not do