voonhous opened a new pull request, #810:
URL: https://github.com/apache/hudi-rs/pull/810
## Description
MinIO turned off anonymous pulls of `quay.io/minio/minio` and
`quay.io/minio/mc`; pulls now fail with `unauthorized: access to the requested
resource is not authorized`. The demo stack that every `integration-tests` job
starts pulls both (the server directly, the client as the build stage of
`demo/infra/mc/Dockerfile`), so those jobs cannot run. This follows
apache/hudi#20058 and takes both images from Chainguard, which are multi-arch
and pull without a login.
- Server: `cgr.dev/chainguard/minio:latest`. It ships `mc`, so the `mc ready
local` healthcheck is unchanged.
- Client: `cgr.dev/chainguard/minio-client:latest-dev`. The plain `latest`
has no shell; `latest-dev` has `sh` and `unzip`, which is everything
`prepare_data.sh` needs. The alpine-based `demo/infra/mc/Dockerfile` is
therefore dropped and the compose service uses the image directly, running the
script as its `entrypoint` (the image's entrypoint is `mc`, so overriding
`command` is not enough).
- CI pre-pulls both images.
Chainguard's free tier publishes only floating tags (`latest`,
`latest-dev`), so the client is no longer pinned to a release as it was in #799.
## How are the changes test-covered
- [ ] N/A
- [x] Automated tests (unit and/or integration tests)
- [x] Manual tests
- [x] Details are described below
Locally, `docker compose up minio mc` in `demo/`: the server reports
healthy, `mc` exits 0, and `hudi-demo` holds the COW and MOR sample tables
(2301 objects). The `integration-tests` jobs on this PR exercise the full stack.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
