[hotfix][ci] Pull MinIO for Milvus tests from Bitnami's legacy image - #1162
Merged
Merged
Conversation
github-actions
Bot
added
doc-not-needed
5 tasks
wenjin272
approved these changes
Sep 28, 2026
wenjin272
left a comment
wenjin272
left a comment
Contributor
There was a problem hiding this comment.
Thanks for fixing this. LGTM.
5 tasks
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.
Linked issue: none (hotfix)
Purpose of change
Restore the Milvus setup in the
cross-languageCI job. Since 2026-09-24 every pull request'scross-languagejob fails at "Start Milvus":quay.io/minio/minionow rejects anonymous pulls (unauthorized: access to the requested resource is not authorized), the same way Docker Hub'sminio/miniodid before #1118. MinIO no longer serves its community image anonymously from either registry.This switches the Milvus compose file to
bitnamilegacy/minio:2025.7.23, a pinned build that still pulls anonymously. That image starts the server itself (API on 9000, console on 9001) and takes its credentials fromMINIO_ROOT_USER/MINIO_ROOT_PASSWORD, so the compose file drops thecommandoverride, sets the credentials tominioadminto match Milvus' default MinIO access key and secret, and mounts the data volume at the image's data directory. The health check probes the API port with bash, because the image does not guaranteecurl; nothing depends on that health check, and the job still waits on Milvus'/healthz.Behavioral Semantics
Not applicable: a CI configuration change with no runtime or API behavior.
Tests
quay.io/minio/minioanddocker.io/minio/miniotag manifests now return 401, whilebitnamilegacy/minio:2025.7.23returns 200.Flink Agents CIon this branch in my fork: thecross-languagejob passes, with Milvus starting against the new image,MilvusVectorStoreTest12/12, and the e2e tests green.API
No public API changes.
Documentation
doc-neededdoc-not-neededdoc-includedWas this patch authored or co-authored using generative AI tooling?
If yes, include a
Generated-by: <tool name and version> (<model name and version>)line, for exampleGenerated-by: Claude Code 2.1.226 (Claude Opus 4.6), in the commit message so it reaches Git history. Repeat the same line here for reviewer visibility. See the ASF generative tooling guidance.Generated-by: Claude Code 2.1.259 (Claude Opus 5.5)