LuciferYang opened a new pull request, #10167: URL: https://github.com/apache/paimon/pull/10167
### Purpose `quay.io/minio/minio:RELEASE.2022-02-07T08-17-33Z`, pinned in `DockerImageVersions.MINIO`, is no longer pullable. MinIO archived its community edition and removed the images from Docker Hub (Sep 2026) and quay.io, so `quay.io/minio/minio` now returns 401 for an anonymous pull. Every test that starts the MinIO container (`S3FileIOTest` and the other `MinioTestContainer` users in `paimon-s3` and `paimon-s3-impl`) fails in CI with `org.testcontainers.containers.ContainerFetchException: Can't get Docker image`. This repoints the pin at `pgsty/silo`, a maintained community MinIO fork that keeps the S3 API, the `MINIO_*` env vars, the `/minio/*` routes, and the `.minio.sys` storage layout, and still accepts the legacy `server <dir>` argv. Only `DockerImageVersions.MINIO` changes; `MinioTestContainer` (its command, env vars, and health probe) is untouched. This follows grafana/mimir#16604, which swapped to the same image and tag. `pgsty/silo` is published on Docker Hub only, so the pin uses `docker.io`. ### Tests No new tests. The existing MinIO-backed tests (`S3FileIOTest` and the other `MinioTestContainer` users) now pull an image that exists; the S3 CI jobs exercise the swap. ### API and Format no ### Documentation no -- 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]
