Repository navigation
chore(compose): run MinIO from the image the test fixture uses - #1608
dimitri-yatsenko wants to merge 1 commit into
Conversation
Sorry, something went wrong.
`docker compose up minio` failed: the service pinned `minio/minio:RELEASE.2025-02-28T09-55-16Z`, and MinIO has withdrawn its Docker Hub images. The `minio_container` fixture moved to `cgr.dev/chainguard/minio:latest` in #1559. The compose service now uses the same image and honors the same `DJ_TEST_MINIO_IMAGE` override. `MINIO_VER` is dropped, since the Chainguard image is published only as `latest`. The Chainguard image runs `/usr/bin/minio` directly, so `command: server ...` still starts the server, but it ships no curl and the old healthcheck could never pass. The healthcheck now runs the bundled `mc ready local`. Credentials move to `MINIO_ROOT_USER`/`MINIO_ROOT_PASSWORD`; the old `MINIO_ACCESS_KEY`/`MINIO_SECRET_KEY` names still work but log a deprecation warning.
|
Closing in favor of #1647, which fixes the same broken docker compose up by moving off MinIO instead of onto the Chainguard build. #1647 replaces the compose minio service with an s3 service on SeaweedFS 4.48, the same image the test fixture now uses. It follows from the evaluation in #1560: MinIO's source is archived, so the Chainguard image only postpones the dependency problem. SeaweedFS matched MinIO's s3fs listing behavior exactly, which garbage collection depends on, and passes the object-storage suites both through testcontainers and through compose with a passing healthcheck. The healthcheck fix here (mc ready local, since the Chainguard image ships no curl) is no longer needed once the service is SeaweedFS. |
Sorry, something went wrong.
docker compose up minio failed: the service pinned minio/minio:RELEASE.2025-02-28T09-55-16Z, and MinIO has withdrawn its Docker Hub images. The minio_container fixture moved to cgr.dev/chainguard/minio:latest in #1559. The compose service now uses the same image and honors the same DJ_TEST_MINIO_IMAGE override. MINIO_VER is dropped, since the Chainguard image is published only as latest.
The Chainguard image runs /usr/bin/minio directly, so command: server ... still starts the server, but it ships no curl and the old healthcheck could never pass. The healthcheck now runs the bundled mc ready local. Credentials move to MINIO_ROOT_USER/MINIO_ROOT_PASSWORD; the old MINIO_ACCESS_KEY/MINIO_SECRET_KEY names still work but log a deprecation warning.