[jira] [Created] (FLINK-40652) MinioTestContainerTest and the S3 e2e tests fail on all release branches because minio/minio was removed from Docker Hub

["Martijn Visser (Jira)" <ji...@apache.org>]

Martijn Visser created FLINK-40652:
--------------------------------------

             Summary: MinioTestContainerTest and the S3 e2e tests fail on all release branches because minio/minio was removed from Docker Hub
                 Key: FLINK-40652
                 URL: https://issues.apache.org/jira/browse/FLINK-40652
             Project: Flink
          Issue Type: Bug
          Components: Build System
    Affects Versions: 1.20.5, 2.2.1, 2.3.0
            Reporter: Martijn Visser


The {{minio/minio}} repository no longer exists on Docker Hub, so every test that starts the MinIO container fails on release-1.20, release-2.2 and release-2.3. master is not affected, FLINK-39499 replaced MinIO with SeaweedFS there.

{code}
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': denied: requested access to the resource is denied"}
{code}

https://hub.docker.com/v2/repositories/minio/minio/ returns {{object not found}}.

The e2e tests fail the same way through {{common_s3_minio.sh}}:

{code}
Spawning minio for s3 tests
docker: Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
[FAIL] Test script contains errors.
{code}

First failing nightly is 2026-09-12, the 2026-09-11 nightly was still green. It reproduces on every profile.

release-2.3: https://github.com/apache/flink/actions/runs/34798011697
release-1.20: https://github.com/apache/flink/actions/runs/34798014224
release-2.2: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=79019

On release-2.2 only the e2e legs show it. Its connect legs fail earlier for unrelated reasons, so no failing test name points at MinIO there.

quay.io still serves the same tag at the same digest ({{sha256:7dda745aefd6152f0d04fdd23377f9e52549df3fc4307f16b8bc562ae2b8119f}}), so pointing {{DockerImageVersions}} and {{common_s3_minio.sh}} at {{quay.io/minio/minio}} restores the previous behaviour. The e2e script pulls the image untagged and needs pinning to the same tag as well, current MinIO images no longer serve a plain bind mounted directory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)