Problem
minio/minio has been removed from Docker Hub, so docker compose -f docker-compose.dev.yml up and the Run Tests with Services CI job both fail at image pull (see PR #58). Upstream MinIO community edition is in maintenance mode, so pinning another MinIO build only postpones this.
Expected behaviour once solved
- The dev stack and CI run Garage (
dxflrs/garage, AGPL-3.0, actively maintained) as the S3-compatible object store.
- It comes up with no manual steps: single-node layout and the access key from
STORAGE_ACCESS_KEY/STORAGE_SECRET_KEY are configured on start (--single-node --default-access-key).
- The API code is unchanged — it already speaks plain S3 through aiobotocore.
Run Tests with Services passes again.- Docs (README,
.env.example, docs/config.md, wiki) describe Garage instead of MinIO.
Why no new dependency is added
It replaces one dev-only container with another; the Python dependencies do not change.
Problem
minio/miniohas been removed from Docker Hub, sodocker compose -f docker-compose.dev.yml upand theRun Tests with ServicesCI job both fail at image pull (see PR #58). Upstream MinIO community edition is in maintenance mode, so pinning another MinIO build only postpones this.Expected behaviour once solved
dxflrs/garage, AGPL-3.0, actively maintained) as the S3-compatible object store.STORAGE_ACCESS_KEY/STORAGE_SECRET_KEYare configured on start (--single-node --default-access-key).Run Tests with Servicespasses again..env.example,docs/config.md, wiki) describe Garage instead of MinIO.Why no new dependency is added
It replaces one dev-only container with another; the Python dependencies do not change.