From 2ad6f21fd3cbcab24a83c165050de8073493fb71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Diego=20Fernando=20Carri=C3=B3n?= Date: Wed, 23 Sep 2026 13:44:15 +0200 Subject: [PATCH] fix(ci): pull MinIO mock from quay.io, Docker Hub images removed MinIO removed its community images from Docker Hub in 2025, so minio/minio:RELEASE.2025-03-12T18-04-18Z now 404s and the s3 and multi-backend functional legs fail at ImagePullBackOff before s3proxy is even installed. Repoint to the still-published quay.io image. Drop --console-address: newer community builds have no embedded console, and the tests only use the S3 API + /minio/health/ready, so the flag is unneeded and keeps the mock working across releases. --- ci/functional/mocks/minio.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ci/functional/mocks/minio.yaml b/ci/functional/mocks/minio.yaml index a47915a..b796cab 100644 --- a/ci/functional/mocks/minio.yaml +++ b/ci/functional/mocks/minio.yaml @@ -19,12 +19,12 @@ spec: spec: containers: - name: minio - image: minio/minio:RELEASE.2025-03-12T18-04-18Z + # quay.io, not docker.io: MinIO removed its community images from Docker + # Hub in 2025, so the old docker.io tag now 404s (ImagePullBackOff). + image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z.hotfix.7aa24e772 args: - server - /data - - --console-address - - ":9001" env: - name: MINIO_ROOT_USER value: minioadmin