fix(ci, selfhost): MinIO is pulled from Quay, not Docker Hub

minio/minio stopped resolving on Docker Hub on 2026-09-16 ("pull access
denied … repository does not exist"), which broke the Integration skeleton
job on a commit that touched nothing near it. The same pinned tag and
digest are on quay.io/minio/minio; the CI workflow and the optional
object-storage profile in the self-host compose file move there.

Author: bridgerahul

.github/workflows/ci.yml

@@ -183,12 +183,13 @@ jobs:
       # Pinned to a release rather than `latest` for the same reason Node and
       # ClickHouse are pinned — a floating tag makes CI results depend on when
       # they ran (D-203).
+      # Quay, not Docker Hub: minio/minio stopped resolving there on 2026-09-16.
       - name: Start MinIO
         run: |
           docker run -d --name minio -p 9000:9000 \
             -e MINIO_ROOT_USER=minioadmin \
             -e MINIO_ROOT_PASSWORD=minioadmin \
-            minio/minio:RELEASE.2025-09-07T16-13-09Z server /data
+            quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z server /data
 
       - name: Wait for MinIO
         run: |

infra/selfhost/docker-compose.yml

@@ -502,8 +502,10 @@ services:
   # S3-compatible object storage, for data import/export. Any S3-compatible
   # provider works; enable this only if you do not already have one.
   #   docker compose --profile object-storage up -d
+  # Pulled from Quay: MinIO's Docker Hub repository stopped resolving on
+  # 2026-09-16 ("pull access denied"); the same tag and digest live on Quay.
   minio:
-    image: minio/minio:RELEASE.2025-09-07T16-13-09Z
+    image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z
     container_name: oa-minio
     restart: unless-stopped
     profiles: ['object-storage']