←back to thread

672 points LexSiga | 5 comments | | HN request time: 0.461s | source
1. c0balt ◴[] No.45666555[source]
I'm glad to have migrated to garage in time. This is quite unfortunate though as a lot of open source projects, like plane.so, used minio via container images for s3 with docker compose.
replies(2): >>45667144 #>>45667305 #
2. Imustaskforhelp ◴[] No.45667144[source]
thoughts on https://github.com/coollabsio/minio ?

I feel like this could be used till the time plane.so or other projects feel like they could migrate to garage or maybe just use these coollabsio minio docker image?

replies(1): >>45667457 #
3. mlrtime ◴[] No.45667305[source]
What did you lose exactly, I don't get it.
replies(1): >>45667450 #
4. c0balt ◴[] No.45667450[source]
Minions has taken away the admin UI for everything except a bucket browser in one of the last releases.

And now they have stopped publishing updates to their community edition docker images. As the linked GitHub issue points out this now means at least one vulnerability will be unpatched (unless you install from source or switch the image) for anyone relying on updates to the original container image.

My loss exactly was that minio lost most of its appeal when it stopped having an integrated management console. It also seemed they were moving into a direction where features were gonna be more separated off for their aistore products over the community edition (a fair move but not something I want to happen to my deployment).

5. c0balt ◴[] No.45667457[source]
My problem was mostly that MinIO was not significantly better for my use-case then garage after the admin console was yanked. Thank you for the pointer though, I will take a look at this for my plane.so instance (using a private containerized minio there still).