Replace MinIO server in tests

[m90]

MinIO is mostly dead these days (it has been replaced with a proprietary offer). The tests still run against a rather old version from August 2020. It would make sense to test against something else that is S3-compatible and also maintained.

I looked into RustFS a while back, but it seemed a little odd to me. Other options would be Garage or a shim layer like Versity.

[szymon-romanko]

I'll try to create PR for this by the end of the week. I've already done some testing with SeaweedFS (more precisely "mini" version, S3-compatible server for testing and development) as an alternative to MiniIO (which has been archived on GitHub a month ago).

[m90]

@szymon-romanko Did you happen to start working on this? The MinIO folks apparently decided to delete the minio/minio repository on Docker Hub in its entirety (we're very welcome), and CI for this repo is currently broken because of that. It seems that minio server images are still around on quay.io, but they don't date back as far as we'd need, so migrating there would also mean having to change some things in the test setup around here.

This makes me think it's probably best to migrate to something entirely different now. If you've been busy, no worries, I can do this myself as well. I just wanted to make sure you're not 99% there already.

[szymon-romanko]

I've started working on this, but at this point its abandoned. Some of my work is available here (also just pushed some old commit drafts i had laying on disk).

The main problem i had with migrating it to SeaweedFS, was that the tests expected files to be easily accessible on the server's filesystem. This is not always the case as s3 is mostly about communication/api and not backend file layout implementation. This is why it wasn't simply a container image swap. I've worked around this using aws-cli and SeaweedFS "mount" feature. Feel free to take my code if you find anything useful there.

[m90]

The main problem i had with migrating it to SeaweedFS, was that the tests expected files to be easily accessible on the server's filesystem.

This is the same problem I ran into when trying to use RustFS.

I just tried porting a single test to use Versity Gateway (which is intended to be a S3 API on top of a plain POSIX FS, thus exactly what the tests need) and it worked as expected. I guess I'll continue down that path then.

Thank you very much for your input and effort, that's much appreciated.