overtrue 5571d4830b test(interop): let the MinIO fixture lab build from registry mirrors ...

The fixture lab's throwaway image hardcoded two Docker Hub base images, so on a network that cannot reach registry-1.docker.io the capture script fails at build time and no MinIO fixtures can be generated at all. That matters more than it looks: the interop reader tests are #[ignore]d precisely because the fixtures are gitignored and must be generated locally, so an unreachable registry silently keeps the whole MinIO SSE interop lane unverifiable.

Both base images become build args with the current Docker Hub values as defaults, and the capture script forwards MINIO_LAB_MINIO_IMAGE / MINIO_LAB_PYTHON_IMAGE when set. CI keeps the defaults; a restricted network can point at quay.io (which publishes the MinIO releases) and public.ecr.aws (which mirrors the official Python images), both verified to produce a working lab image and real fixtures.

The README documents the override and warns against an unpinned :latest MinIO tag, since the captured on-disk format is exactly what the interop tests assert against.

Refs rustfs/backlog#1638.

2026-08-16 21:23:17 +08:00

..

src

fix(rio-v2): detect DARE stream truncation at package boundary (#4585)

2026-07-09 05:44:32 +08:00

tests

test(interop): let the MinIO fixture lab build from registry mirrors

2026-08-16 21:23:17 +08:00

Cargo.toml

feat: extend hotpath coverage across crates (#5505)

2026-07-31 05:42:19 +00:00