Repository navigation
fix(ci): pull MinIO from Chainguard — quay.io/minio/minio is no longer public either - #4378
Merged
Merged
Conversation
…r public either #4208 moved the "Start MinIO" step from docker.io to quay.io after Docker Hub stopped serving minio/minio. quay.io/minio/minio now answers "unauthorized" to anonymous pulls for every tag and for the pinned digest, so every go.yml run fails at "Start MinIO" with exit 125. Checked anonymously on 2026-09-25: - docker.io/minio/minio -> requested access to the resource is denied - quay.io/minio/minio -> 401 unauthorized (repo, tag and digest) - docker.io/bitnami/minio -> manifest unknown - dl.min.io binaries -> 410 Gone - cgr.dev/chainguard/minio -> pullable, linux/amd64 + arm64 cgr.dev/chainguard/minio is MinIO built from upstream AGPL source (RELEASE.2026-09-22T19-25-18Z at the pinned digest) with /usr/bin/minio as its entrypoint, so the existing `server /data` args and the /minio/health/live readiness poll are unchanged. Still pinned by digest. Verified: ran the pinned image with `server /data` and the step's env, then `S3_REQUIRE_MINIO=true go test ./...` in examples/using-s3-filestore: TestS3FileStore_RoundTrip and TestS3FileStore_CopyAndReadAt both PASS. The example README pointed users at the same dead quay.io image; updated.
Umang01-hash
approved these changes
Sep 25, 2026
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
2 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.
Why
Every
go.ymlrun is failing at Start MinIO (exit 125):#4208 moved this step from Docker Hub to
quay.io/minio/minio11 days ago. MinIO has since closed quay.io to anonymous pulls too, for every tag and for the pinned digest.What's still pullable (checked anonymously, 2026-09-25)
docker.io/minio/minioquay.io/minio/miniodocker.io/bitnami/miniodl.min.iobinariescgr.dev/chainguard/minioChange
.github/workflows/go.yml: image →cgr.dev/chainguard/minio@sha256:bd014394…65ae1, still pinned by digest. It is real MinIO built from upstream AGPL source (RELEASE.2026-09-22T19-25-18Z), entrypoint/usr/bin/minio, soserver /data, the env and the/minio/health/livepoll are unchanged.examples/using-s3-filestore/README.md: pointed at the same dead quay.io image; updated.Verified
Ran the pinned image with
server /dataand the step's env, then inexamples/using-s3-filestore:The #3804 guard stays required:
S3_REQUIRE_MINIOand the fail-loud readiness loop are untouched.Risk
Chainguard's free tier only publishes
latest. A digest pin keeps us on a fixed build, but if Chainguard ever garbage-collects that digest this step fails loudly (same as today) rather than silently skipping — bump the digest then.