Live data from Hacker News

MinIO Is Dead, Long Live MinIO

blog.vonng.com

41–50 of 95 posts

Re: MinIO Is Dead, Long Live MinIO

#41
post #10

Seems like a very balanced take on forking Minio. I don't have high hopes for the future Minio, but as mentioned it is more or less feature complete, good enough for most use-cases. I was searching for a fairly simple replacement for s3 for testing. I'd been using Minio for a while now, and simply ended up implementing my own on top of Postgres. Fun intersection given the post. (Note, I know it isn't optimal, but as…

For our needs at work (~100TB), buying Pure Storage flash arrays (hardware, software, onsite support) worked out cheaper than MinIO licensing alone.

It is an interesting time we're in right now where buying physical hardware and support is cheaper than a license.

Same goes for AWS markup on rented hardware. ;)

Man I sometimes miss having physical servers.

Re: MinIO Is Dead, Long Live MinIO

#42

I'll plug that Chainguard has been maintaining a fork for awhile and seems to have a history with supporting forks like this: https://github.com/chainguard-forks/minio For a web GUI, I had been using this project: https://github.com/huncrys/minio-console I switched to rustfs this week though and am not looking back. I'd recommend it to others as well for small scale usage. Its maturing rapidly and seems promising.

Do note rustfs has had a...questionable...security posture. See https://github.com/rustfs/rustfs/security/advisories/GHSA-h9... as a good example (hardcoded static token).

Re: MinIO Is Dead, Long Live MinIO

#43
post #10

Seems like a very balanced take on forking Minio. I don't have high hopes for the future Minio, but as mentioned it is more or less feature complete, good enough for most use-cases. I was searching for a fairly simple replacement for s3 for testing. I'd been using Minio for a while now, and simply ended up implementing my own on top of Postgres. Fun intersection given the post. (Note, I know it isn't optimal, but as…

I've been using garage without issue

I considered it a while ago, but I wasn't totally clear on Read-After-Write. Which was the primary reason why I choose to just implement my own for testing.

I'll probably give GarageHQ a more serious look again.

Re: MinIO Is Dead, Long Live MinIO

#46
post #34

Also see Garage S3: https://garagehq.deuxfleurs.fr/

Moved to Garage, it's actually pretty easy to run and use.

Would be even nicer if the official Docker image would support initializing a default bucket and access key from env variables instead of having to exec into the container and follow https://garagehq.deuxfleurs.fr/documentation/quick-start/ but that's not a dealbreaker.

Note: I only needed the single-node install, it was either this or SeaweedFS. Also used MinIO and Zenko in the past, but even the latter seems pretty much dead.

Re: MinIO Is Dead, Long Live MinIO

#48
> A company that raised $126M at a billion-dollar valuation spent five years methodically dismantling the open-source ecosystem it built.

Sounds like Puppet's story. $180M raised, ~$1B valuation ca. 2019, sold to Perforce in 2022, public repo taken private and builds commercialized by Perforce in 2024, community fork shipped early 2025.

Re: MinIO Is Dead, Long Live MinIO

#49

I'll plug that Chainguard has been maintaining a fork for awhile and seems to have a history with supporting forks like this: https://github.com/chainguard-forks/minio For a web GUI, I had been using this project: https://github.com/huncrys/minio-console I switched to rustfs this week though and am not looking back. I'd recommend it to others as well for small scale usage. Its maturing rapidly and seems promising.

The README doesn't seem to have been updated, is there an updated Docker image to use now?

Edit:

https://hub.docker.com/r/pgsty/minio

From the OP's link

Re: MinIO Is Dead, Long Live MinIO

#50

AGPL is a plague. So many possible partners or future stewards won’t touch anything minIO with a ten foot pole unfortunately. And I say this because minIO started to actively engage on the ugly parts of the license

AGPL is "a plague" by design (viral). It has the explicit goal that any improvements flow back to the community project and the virality is a necessary building block for this. It is an elegant solution to a tragedy of the commons problem.

Companies like MinIO extending the virality beyond the single software/work, even though not intended by license, gives it a bad reputation. They have fixed https://min.io/compliance now, but I guess it does not matter anymore.

Post reply on HN