fix(dev): pull minio mc client from quay.io

MinIO removed the mc client image from Docker Hub, so 'minio/mc:latest' now
fails with 'pull access denied / authentication required' and breaks the dev
minio-init container (spin up / docker compose up). Repoint minio-init to
quay.io/minio/mc:latest (MinIO's own registry, pullable without login) in the
dev, maxio, and dev-multi compose files. The minio server image
(coollabsio/maxio:latest) still pulls fine and is unchanged.

docker-compose-maxio.dev.yml

@@ -182,7 +182,8 @@ services:
   #   networks:
   #     - coolify
   minio-init:
-    image: minio/mc:latest
+    # MinIO removed the mc client from Docker Hub; pull it from MinIO's own registry.
+    image: quay.io/minio/mc:latest
     pull_policy: always
     container_name: coolify-minio-init
     restart: no

docker-compose.dev-multi.yml

@@ -195,7 +195,8 @@ services:
 
   minio-init:
     profiles: ["minio"]
-    image: minio/mc:latest
+    # MinIO removed the mc client from Docker Hub; pull it from MinIO's own registry.
+    image: quay.io/minio/mc:latest
     pull_policy: always
     restart: "no"
     depends_on:

docker-compose.dev.yml

@@ -150,7 +150,8 @@ services:
     networks:
       - coolify
   minio-init:
-    image: minio/mc:latest
+    # MinIO removed the mc client from Docker Hub; pull it from MinIO's own registry.
+    image: quay.io/minio/mc:latest
     pull_policy: always
     container_name: coolify-minio-init
     restart: no