FrankChen021 opened a new pull request, #20331:
URL: https://github.com/apache/druid/pull/20331

   ## Description
   
   The `minio/minio:latest` image is no longer publicly pullable from Docker 
Hub. Testcontainers therefore fails to create MinIO containers with errors such 
as:
   
   ```
   ContainerFetchException
   404: pull access denied for minio/minio
   repository does not exist or may require docker login
   ```
   
   This failure was observed in the CI runs for [PR 
#20329](https://github.com/apache/druid/pull/20329) and [PR 
#20330](https://github.com/apache/druid/pull/20330).
   
   This change switches Druid's MinIO test image from:
   
   ```
   minio/minio:latest
   ```
   
   to:
   
   ```
   quay.io/minio/minio:latest
   ```
   
   The reference is updated in the shared GitHub Actions pre-pull step and the 
three S3/embedded test container definitions.
   
   Testcontainers validates that `MinIOContainer` receives a compatible image 
name, so the Quay image is explicitly declared as a compatible substitute for 
`minio/minio`.
   
   ## Licensing
   
   The registry change does not change the image license. This remains the 
official MinIO Community Edition image; MinIO server source is licensed under 
[AGPLv3](https://github.com/minio/minio/blob/master/LICENSE). The image is used 
only as an external test service and is not packaged into Druid artifacts.
   
   ## Testing
   
   - `MinIOStorageResourceTest` and `MinIOStorageTest`: 6 tests passed.
   - `ServerSideEncryptingAmazonS3MultipartUploadTest` and 
`S3StorageConnectorTest`: 14 tests passed with the `ci` profile.
   - `git diff --check` passed.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to