aicam opened a new pull request, #8529:
URL: https://github.com/apache/texera/pull/8529
### What changes were proposed in this PR?
Docker Hub no longer serves `minio/minio` or `minio/mc`. As a result, every
job that starts MinIO is currently red on `main` and on open PRs (e.g. #6896):
`amber`, `amber-integration`, `platform (file-service)` and
`platform-integration (file-service)`. They fail with:
```
pull access denied for minio/minio, repository does not exist or may require
'docker login'
```
This PR switches every MinIO image reference to MinIO's official mirror on
`quay.io`, keeping the **same pinned tags**. The images there are
byte-identical to the ones CI used before:
| image | old Docker Hub image ID | quay.io image ID |
|---|---|---|
| `minio:RELEASE.2025-02-28T09-55-16Z` | `sha256:a929054a…` |
`sha256:a929054a…` |
| `mc:RELEASE.2025-05-21T01-59-54Z` | `sha256:09f93f53…` |
`sha256:09f93f53…` |
Only the registry changes; MinIO behavior doesn't.
Non-obvious bits:
- Testcontainers' `MinIOContainer` calls
`assertCompatibleWith("minio/minio")` and rejects any other image name. The
Scala test fixtures therefore mark the quay.io image with
`.asCompatibleSubstituteFor("minio/minio")`.
- The untagged `minio/mc` in the platform-integration bucket step is now
pinned to the same `mc` release that `bin/single-node` uses.
- The macOS path (`brew install minio/stable/minio`) is unaffected. The tap
still exists; that job only showed as failed because fail-fast cancelled it.
- `bin/k8s` uses `bitnamilegacy/minio`, which isn't affected, so it's left
alone.
### Any related issues, documentation, discussions?
The breakage is visible on #6896 and every other PR that runs the
MinIO-backed jobs.
### How was this PR tested?
- **Testcontainers specs, run locally with this branch:**
- `WorkflowCore/testOnly S3StorageClientSpec LakeFSStorageClientMtimeSpec
LargeBinaryManagerSpec`: 73 passed.
- `FileService/testOnly DatasetResourceSpec` (via `MockLakeFS`): 152
passed.
- The logs show containers created from
`quay.io/minio/minio:RELEASE.2025-02-28T09-55-16Z`.
- `WorkflowCore/Test/scalafmtCheck` and `FileService/Test/scalafmtCheck`
pass.
- **Full `bin/single-node` stack with the updated compose file:**
- All services came up healthy, including `minio`, `minio-init` (bucket
created by quay.io `mc`), `lakefs`, `lakekeeper` and `file-service`.
- End to end, I logged in, created a dataset, uploaded a file (200), and
committed a version. The LakeFS objects for it appeared in the `texera-dataset`
bucket in MinIO.
- This PR's own CI run covers the workflow changes.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_0127YDvJ55zTd2x2RpRjK5GF
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
