test: run MinIO from bitnamilegacy/minio; Quay now requires a login

[yarikoptic-gitmate]

On 2026-09-24 MinIO made quay.io/minio/minio (and minio/mc) require authentication. Since then, docker compose pull of the test archive fails with minio Error unauthorized: access to the requested resource is not authorized, and every Docker-backed test errors during setup. This affects this repo's tests and downstream users of this compose file; backups2datalad CI is red for this reason (dandi/backups2datalad#124, dandi/backups2datalad#125). It is the follow-up to #1921, which moved us to Quay after minio/minio was deleted from Docker Hub.

Change

• Switch dandi/tests/data/dandiarchive-docker/docker-compose.yml to bitnamilegacy/minio:latest. This is the image dandi-archive's backend/frontend CI already uses.
• The Bitnami image starts the server itself, keeping its data under /bitnami/minio/data, and takes the same MINIO_ROOT_USER/MINIO_ROOT_PASSWORD. So the command override goes, and the tty that was only there for printing credentials goes too.
• The existing curl healthcheck still works, since the image ships curl and mc.

This image is frozen too. dandi/dandi-infrastructure#289 is about hosting a copy of our own; once that exists, this line should point there.

Testing

• docker compose pull of this compose file succeeds.
• docker compose up --wait minio reports the service healthy, and /minio/health/live returns 200.
• With the test credentials, boto3 against 127.0.0.1:9000 could create the bucket, enable versioning, and put/get an object.
• I could not run the full Docker-based test suite here: the django container can't reach PyPI from my sandbox, which has nothing to do with MinIO. CI here will exercise it.

Suggested label: tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KoaLJfNiVVnwSDHNMg2bpK

---

Generated by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.11%. Comparing base (e88467d) to head (f453137).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1927      +/-   ##
==========================================
- Coverage   78.14%   78.11%   -0.03%     
==========================================
  Files          91       91              
  Lines       13944    13944              
==========================================
- Hits        10896    10893       -3     
- Misses       3048     3051       +3     

Flag	Coverage Δ
unittests	78.11% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[yarikoptic-gitmate]

CI note on test (ubuntu-latest, 3.11, dev-deps): it fails in the "Install dev versions of select dependencies" step before any test runs. The error is ERROR: Package 'hdmf-zarr' requires a different Python: 3.11.16 not in '>=3.12'. hdmf-zarr's development branch now requires Python ≥ 3.12, and this matrix entry runs 3.11, so every PR will hit this until the workflow changes. It isn't caused by the compose change here. I didn't find an open PR that fixes it.

Proposed fix, kept separate so this PR stays a one-line change: in .github/workflows/run-tests.yml, run the first dev-deps entry on '3.12' instead of '3.11', or drop it, since there's already a 3.14 dev-deps entry. Happy to open that if wanted.

codecov/project was computed from the few jobs that had finished at the time; it should settle once the full matrix reports.

---

Generated by Claude Code

[yarikoptic]

dev-deps is independent

• started to fail to "install" in dandi-cli dev testing, needing python 3.12 min? can 3.11 still be ok? hdmf-dev/hdmf-zarr#406

[github-actions]

🚀 PR was released in 0.80.1 🚀