nevzheng opened a new issue, #13111:
URL: https://github.com/apache/gravitino/issues/13111
### Version
main branch
### Describe what's wrong
Integration tests that start `MinIOContainer` fail because the image
`minio/minio:RELEASE.2025-09-07T16-13-09Z` can no longer be pulled from Docker
Hub. The `minio/minio` and `minio/mc` repositories return 404 from the Docker
Hub API, while the `minio` organization still exists. The same release is
available on quay.io. This fails Backend Integration Test
(`FilesetS3TokenConnectionIT`) for every PR since 2026-09-12;
`IcebergRESTMinIOTokenAuthorizationIT` uses the same container.
### Error message and/or stacktrace
```
FilesetS3TokenConnectionIT > initializationError FAILED
java.lang.RuntimeException: Failed to start MinIO container
org.testcontainers.containers.ContainerFetchException: Can't get
Docker image:
RemoteDockerImage(imageName=minio/minio:RELEASE.2025-09-07T16-13-09Z, ...)
com.github.dockerjava.api.exception.NotFoundException: Status
404: {"message":"pull access denied for minio/minio, repository does not exist
or may require 'docker login'"}
```
### How to reproduce
```
docker pull minio/minio:RELEASE.2025-09-07T16-13-09Z # pull access
denied
docker pull quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z # succeeds
```
### Additional context
The image is referenced only in
`integration-test-common/src/test/java/org/apache/gravitino/integration/test/container/MinIOContainer.java`
(`DEFAULT_IMAGE`). The last passing Backend Integration Test on `main` ran at
2026-09-12 02:28 UTC.
--
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]
