Switch the minio service image from quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z to bitnamilegacy/minio:2025.7.23-debian-12-r5 — the old quay.io tag no longer exists on the registry (docker manifest inspect -> "no such manifest"), so fresh deployments can never start the minio service.
Changes:
minio image -> bitnamilegacy/minio:2025.7.23-debian-12-r5, run as root, bitnami entrypoint/run scripts, data volume at /bitnami/minio/data
minio-initialize.sh: isolate MC_CONFIG_DIR=/tmp/mc-drive-init so the bucket-creation script (running as root) doesn't collide with the Bitnami image's internal mc client config
Switch the minio service image from `quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z` to `bitnamilegacy/minio:2025.7.23-debian-12-r5` — the old quay.io tag no longer exists on the registry (`docker manifest inspect` -> "no such manifest"), so fresh deployments can never start the minio service.
Changes:
- minio image -> `bitnamilegacy/minio:2025.7.23-debian-12-r5`, run as root, bitnami entrypoint/run scripts, data volume at `/bitnami/minio/data`
- `minio-initialize.sh`: isolate `MC_CONFIG_DIR=/tmp/mc-drive-init` so the bucket-creation script (running as root) doesn't collide with the Bitnami image's internal `mc` client config
Mirrors upstream PR: https://git.coopcloud.tech/coop-cloud/lasuite-drive/pulls/13
**Verified on cctest** (chaos deploy of 782e3f0):
- minio service `Up (healthy)` with the bitnami image, `mc ready local` healthcheck passing
- bucket `drive-media-storage` auto-created + versioning enabled via the isolated MC_CONFIG_DIR
- minio endpoint through Traefik returns HTTP 200
- all 11 services converged; all automated tests pass (health_check, wopi_configured, wopi_on_startup, celery_beat_wopi, oidc_login)
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Switch the minio service image from
quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Ztobitnamilegacy/minio:2025.7.23-debian-12-r5— the old quay.io tag no longer exists on the registry (docker manifest inspect-> "no such manifest"), so fresh deployments can never start the minio service.Changes:
bitnamilegacy/minio:2025.7.23-debian-12-r5, run as root, bitnami entrypoint/run scripts, data volume at/bitnami/minio/dataminio-initialize.sh: isolateMC_CONFIG_DIR=/tmp/mc-drive-initso the bucket-creation script (running as root) doesn't collide with the Bitnami image's internalmcclient configMirrors upstream PR: https://git.coopcloud.tech/coop-cloud/lasuite-drive/pulls/13
Verified on cctest (chaos deploy of
782e3f0):Up (healthy)with the bitnami image,mc ready localhealthcheck passingdrive-media-storageauto-created + versioning enabled via the isolated MC_CONFIG_DIRcc @trav @notplants
!testme
🌻 cc-ci —
lasuite-drive@782e3f09❌ failurefull logs · dashboard
!testme
🌻 cc-ci —
lasuite-drive@782e3f09❌ failurefull logs · dashboard
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed