From 6c52ad655e4b933bc1dc82593718325ac1ecb5e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cau=C3=AA=20Faleiros?= Date: Mon, 21 Sep 2026 12:33:46 -0300 Subject: [PATCH] fix: pull MinIO from quay.io so CI can start the stack The integration job failed on the runner with "pull access denied for minio/minio ... may require 'docker login'". Docker Hub now refuses anonymous pulls of minio/minio: an unauthenticated manifest request returns 401 UNAUTHORIZED, while library/postgres returns 200, which is why only MinIO failed. It worked locally only because this machine is logged in to Docker Hub. quay.io serves the same release anonymously, and it is the same image: both registries resolve to image ID sha256:a1ea29fa2835. MINIO_IMAGE overrides it for anyone mirroring into their own registry. Verified by deleting the Docker Hub copy locally and starting the stack from quay alone, then running the full suite against it. Co-Authored-By: Claude Opus 5 --- compose.local.yaml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/compose.local.yaml b/compose.local.yaml index 8d64c46..f4e342e 100644 --- a/compose.local.yaml +++ b/compose.local.yaml @@ -65,7 +65,11 @@ services: retries: 30 storage: - image: minio/minio:RELEASE.2025-04-22T22-12-26Z + # quay.io, not Docker Hub: minio/minio there now answers anonymous pulls + # with 401 authentication required, which breaks any runner that is not + # logged in. Same image — identical image ID. Override MINIO_IMAGE to use + # a mirror of your own. + image: ${MINIO_IMAGE:-quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z} command: server /data --console-address :9001 environment: MINIO_ROOT_USER: ${MINIO_ROOT_USER:-dtf_local} @@ -95,7 +99,7 @@ services: restart: on-failure storage-init: - image: minio/minio:RELEASE.2025-04-22T22-12-26Z + image: ${MINIO_IMAGE:-quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z} entrypoint: [/bin/sh, /init.sh] environment: MINIO_ROOT_USER: ${MINIO_ROOT_USER:-dtf_local}