this is happening again and breaking standard system test CI [immagine] Minio installer breaks CI Development The minio_runner’s install script is broken, because of a redirect that’s not being followed. That breaks the shared GitHub action workflows from the .github repository. For our plugins, this means, we cannot run Rails system tests on CI at the moment. They start, but as the setup cannot be completed, they stay red even before the first test runs red_circle. Run bundle exec ruby script/install_minio_binaries.rb /__w/zlb-community/zlb-community/vendor/bundle/ruby/3.4.0/gems/minio_runner-1.0.0… The standard Discourse plugin system-test CI failed during its shared MinIO environment setup. The MinIO client download returned HTTP 410 before any plugin system tests ran.

just acking this one and I’m looking. seems like the upstream builds have disappeared.

Yeah. Looks like: Both minio/minio and minio/mc are now archived. MinIO’s README says “Alternatives:* AIStor Free — Full-featured, standalone edition for community use (free license)” MinIO’s README also says “Important: The MinIO community edition is now distributed as source code only. We will no longer provide pre-compiled binary releases for the community version.” I’m not sure if AIStor is a simple drop-in replacement? Given this simply just doesn’t work now, is it better to disable this dependency and skip any tests that rely upon it in interim? I appreciate specs are critical but I believe this is only used on a tiny percentage of tests. Does this break production in some way? From my analysis, impact looks limited to specs?

I came across something similar when I noticed that Minio is a dependency of one of the services I use, and just yesterday I was evaluating alternatives. It seems that the lightweight and most developed option is https://garagehq.deuxfleurs.fr/, while the most comprehensive one (still in development and possibly not yet ready for production) is RustFS · GitHub

yeah, RustFS looks like the best potential from a quick look but it’s not drop in either. currently, I’m working on just forking those two repos and creating a workflow that will build the binary for us.

[immagine] ducks: RustFS looks like the best potential from a quick look From S3 Compatibility Matrix Capability Status Scope ACL authorization :cross_mark: Excluded Intentionally unsupported product behavior Garage is missing the necessary ACL functionality as well.

L'installer di MinIO fallisce di nuovo, stavolta con un errore HTTP 410

Assistenza prodotto

ducks (on the pond) 12 Settembre 2026, 10:45pm 2

Segnalo solo questo punto e sto già controllando. Sembra che le build upstream siano scomparse.

Argomento		Risposte	Visualizzazioni
Minio installer breaks CI Development development , bug	2	248	Aprile 29, 2026
S3 migrations from/to minio problems Bug	45	5585	Marzo 19, 2019
Forum rendered unusable Self-hosting s3	10	1080	Settembre 4, 2023
Has anyone succeed in use minio for upload files? Product Support	7	1409	Novembre 12, 2019
Backup is failing due to bad HTTPS Product Support unsupported-install	19	2093	Aprile 1, 2019

L'installer di MinIO fallisce di nuovo, stavolta con un errore HTTP 410

Argomenti correlati