LuciferYang opened a new pull request, #9780:
URL: https://github.com/apache/paimon/pull/9780
### Purpose
Every container test that starts `MinioTestContainer` now fails before the
test body runs:
```
org.testcontainers.containers.ContainerFetchException: Can't get Docker
image:
RemoteDockerImage(imageName=minio/minio:RELEASE.2022-02-07T08-17-33Z, ...)
Caused by: com.github.dockerjava.api.exception.NotFoundException: Status 404:
{"message":"pull access denied for minio/minio, repository does not exist
or may require 'docker login'"}
```
MinIO stopped publishing its Community Edition images and the Docker Hub
`minio/minio` repository is gone, so the unqualified name no longer resolves.
Re-running does not help. `paimon-s3-impl` fails in `S3FileIOTest`, which means
any PR whose reactor reaches that module goes red: a `paimon-common` change now
fails CI for a reason that has nothing to do with it.
MinIO's own quay.io registry still serves the same
`RELEASE.2022-02-07T08-17-33Z` tag publicly, so qualifying the name is enough
to restore the pull. It is the same image at the same version, so its license
is unchanged; only the registry differs. `quay.io/minio/minio` is MinIO's own
organization namespace, and several ASF projects already pull it from there,
among them `apache/iceberg`, `apache/hudi`, `apache/doris` and `apache/opendal`.
`DockerImageVersions.MINIO` is the only place the image is named.
`paimon-s3`, `paimon-s3-impl` and `paimon-flink-cdc` reach it through
`MinioTestContainer`.
### Tests
The quay.io tag is anonymously pullable (its registry manifest returns 200)
while Docker Hub returns 404 for the same tag. `paimon-test-utils` and
`paimon-s3-impl` compile, with checkstyle and spotless clean. I have no Docker
locally, so CI covers the container startup itself.
--
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]
