Use other minio as the quay.io is not available

Reviewed-on: https://git.coopcloud.tech/coop-cloud/lasuite-docs/pulls/25

compose.yml

@@ -110,7 +110,7 @@ services:
       labels:
         - "traefik.enable=false"
         - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
-        - "coop-cloud.${STACK_NAME}.version=0.4.1+v5.6.1"
+        - "coop-cloud.${STACK_NAME}.version=0.4.2+v5.6.1"
     user: "${DOCKER_USER:-1000}"
     healthcheck:
       test: ["CMD", "curl", "-f", "http://localhost:8080"]
@@ -253,7 +253,8 @@ services:
       - backend
 
   minio:
-    image: minio/minio:RELEASE.2025-09-07T16-13-09Z
+    image: bitnamilegacy/minio:2025.7.23-debian-12-r5
+    user: root
     environment: *minio-env
     healthcheck:
       test: ["CMD", "mc", "ready", "local"]
@@ -262,11 +263,11 @@ services:
       retries: 300
     networks:
       - backend
-    command: minio server /data
+    command: /opt/bitnami/scripts/minio/run.sh
     entrypoint: >
-      sh -c "/minio-initialize.sh & exec /usr/bin/docker-entrypoint.sh \"$$@\"" --
+      sh -c "/minio-initialize.sh & exec /opt/bitnami/scripts/minio/entrypoint.sh \"$$@\"" --
     volumes:
-      - minio:/data
+      - minio:/bitnami/minio/data
     deploy:
       labels:
         backupbot.backup: "${ENABLE_BACKUPS:-true}"

minio-initialize.sh

@@ -1,6 +1,11 @@
 #!/bin/sh
 set -e
 
+# Use an isolated mc config dir: the bundled Bitnami image runs its own
+# internal mc client (as the "minio" user) against the default /.mc path,
+# which collides with this script running as root against the same path.
+export MC_CONFIG_DIR=/tmp/mc-docs-init
+
 # Wait for minio to be ready (up to 60 seconds)
 i=0
 while ! mc ready local 2>/dev/null; do