CI: MinIO-backed tests fail because Docker Hub no longer serves minio/minio

[jiayuasu]

Expected behavior

OsmReaderTest ("should be able to read from osm file on s3") and the S3 test in GeoPackageReaderTest start a MinIO container through Testcontainers and pass, as they did on every master run up to 2026-09-11 07:18 UTC.

Actual behavior

Since 2026-09-11 about 19:20 UTC every Scala and Java build run fails as soon as the first MinIO-backed test starts:

org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=minio/minio:latest, imagePullPolicy=DefaultPullPolicy(), ...)
  at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1308)
  at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:346)
  at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
  at org.apache.sedona.sql.OsmReaderTest.$anonfun$new$6(OsmReaderTest.scala:113)
  ...
  Cause: com.github.dockerjava.api.exception.NotFoundException: Status 404: {"message":"pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"}

The minio/minio repository is no longer on Docker Hub: https://hub.docker.com/v2/repositories/minio/minio/ returns 404 while the minio organisation and its other repositories still resolve, and the registry answers UNAUTHORIZED for a pull token. MinIO still publishes the same images on quay.io (quay.io/minio/minio; latest currently points at RELEASE.2025-09-07T16-13-09Z).

The matrix runs with fail-fast, so the one failing job cancels the rest and the workflow is red for every PR. First seen on #3353 (both attempts) and on the master run after a870e2b.

Steps to reproduce

Open any PR, or run docker pull minio/minio:latest.

Settings

Sedona version = master

API type = Scala

Spark version = all

Environment = GitHub Actions