test(cm-files): pull MinIO from quay.io — Docker Hub no longer has the repository
deploy / test (push) Successful in 4m57s
deploy / build (push) Successful in 5m49s

`cargo test --workspace` fails on any fresh machine: hub.docker.com's
minio/minio returned 404 for the whole repository on 2026-09-19, and
testcontainers cannot pull it. CI on gw-04 kept passing because a year-old
copy is cached there and testcontainers pulls only when the local create
returns 404 — one image prune away from failing forever, and already failing
here. MinIO publishes the same image on quay.io; the manifest answers 200.

Found while reproducing a red CI run that turned out to be environmental.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01WZb5A2kfVfjpdwSochkuHz
This commit is contained in:
Omar Sobh
2026-09-18 23:39:40 -05:00
co-authored by Claude Opus 5
parent 8e4b2e4a12
commit 5d9edd636d
+5 -1
View File
@@ -11,7 +11,11 @@ async fn minio_store() -> (
S3BlobStore,
testcontainers_modules::testcontainers::ContainerAsync<GenericImage>,
) {
let container = GenericImage::new("minio/minio", "latest")
// quay.io, not Docker Hub: hub.docker.com/r/minio/minio returned 404 for
// the whole repository on 2026-09-19. CI kept passing only because gw-04
// had a year-old copy cached and testcontainers pulls only on a local
// miss; every fresh machine failed here with "pull access denied".
let container = GenericImage::new("quay.io/minio/minio", "latest")
.with_exposed_port(9000.tcp())
.with_wait_for(WaitFor::message_on_either_std("API:"))
.with_env_var("MINIO_ROOT_USER", "tc-access")