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.
MinIO gated quay.io/minio/minio behind authentication (~Sep 24-25 2026, moving OSS images to the paid AIStor registry) — anonymous pulls return "no such manifest"/401, so fresh deployments can never start the minio service. The minio/minio Docker Hub repo was already removed entirely. References:
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-docs-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`.
MinIO gated `quay.io/minio/minio` behind authentication (~Sep 24-25 2026, moving OSS images to the paid AIStor registry) — anonymous pulls return "no such manifest"/401, so fresh deployments can never start the minio service. The `minio/minio` Docker Hub repo was already removed entirely. References:
- https://www.ibm.com/support/pages/node/7289585 (Sep 25: "MinIO Image Removal from Quay Registry")
- https://github.com/milvus-io/milvus/issues/53430 (Sep 14: Docker Hub repo gone)
Changes (identical to the verified lasuite-drive fix — https://git.coopcloud.tech/coop-cloud/lasuite-drive/pulls/13, verified end-to-end on cctest: healthy minio, bucket auto-created + versioning enabled, all tests pass):
- 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-docs-init` so the bucket-creation script (running as root) doesn't collide with the Bitnami image's internal `mc` client config
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.MinIO gated
quay.io/minio/miniobehind authentication (~Sep 24-25 2026, moving OSS images to the paid AIStor registry) — anonymous pulls return "no such manifest"/401, so fresh deployments can never start the minio service. Theminio/minioDocker Hub repo was already removed entirely. References:Changes (identical to the verified lasuite-drive fix — https://git.coopcloud.tech/coop-cloud/lasuite-drive/pulls/13, verified end-to-end on cctest: healthy minio, bucket auto-created + versioning enabled, all tests pass):
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-docs-initso the bucket-creation script (running as root) doesn't collide with the Bitnami image's internalmcclient configcc @trav @notplants
!testme
🌻 cc-ci —
lasuite-docs@c4e13100❌ failurefull logs · dashboard
!testme
🌻 cc-ci —
lasuite-docs@c4e13100❌ failurefull logs · dashboard
autonomic-bot referenced this pull request2026-09-28 21:05:00 +00:00
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed