←back to thread

MinIO stops distributing free Docker images

(github.com)
672 points LexSiga | 4 comments | 22 Oct 25 06:17 UTC | HN request time: 0.001s | source
Show context
mattbee ◴[22 Oct 25 10:53 UTC] No.45667259[source]▶
They abandoned documentation (edit: for the open source codebase) a couple of weeks ago - that seems more significant.

From their Slack on Oct 10:

"The documentation sites at docs.min.io/community have been pulled of this morning and will redirect to the equivalent AIStor documentation where possible". [emphasis mine]

The minio/docs repository hasn't been updated in 2 weeks now, and the implication is that isn't going to be.

Even when I set up a minio cluster this February, it was both impressively easy and hard in a few small aspects. The most crucial installation tips - around 100Gb networking, Linux kernel tunables and fault-finding - were hung off comments on their github, talking about files that were deleted from the repository years ago.

I've built a cluster for a client that's being expanded to ≈100PB this year. The price of support comes in at at slightly less than the equivalent amount of S3 storage (not including the actual hosting costs!). The value of it just isn't that high to my client - so I guess we're just coasting on what we can get now, and will have to see what real community might form around the source.

I'm not a free software die-hard so I'm grateful for the work minio have put into the world, and the business it's enabling. But it seems super-clear they're stopping those contributions, and I'd bet the final open source release will happen in the next year.

If anyone else is hosting with minio & can't afford the support either :) please drop me a line and maybe we can get something going.

replies(6): >>45668446 #>>45668529 #>>45668617 #>>45670374 #>>45670759 #>>45672247 #
1. gr4vityWall ◴[22 Oct 25 13:08 UTC] No.45668529[source]▶
That does sound much worse than hiding the pre-built images from users. I hope that documentation is archived. There's probably some benefit in documenting those installation tips elsewhere besides Github comments.
replies(3): >>45670242 #>>45671999 #>>45673791 #
2. empyrrhicist ◴[22 Oct 25 15:04 UTC] No.45670242[source]▶
I'm sure it's been scraped to be regurgitated by a whole slew of LLMs.
3. knowitnone3 ◴[22 Oct 25 16:59 UTC] No.45671999[source]▶
old documentation doesn't help when the software changes
4. soraminazuki ◴[22 Oct 25 19:14 UTC] No.45673791[source]▶
Yeah, running binaries of varying qualities taken from all sorts of places is a bad idea anyways. Distro packages are generally more consistent or even running "go build" yourself is probably better in this case.

But pulling existing documentation is a whole different matter. One can argue that they don't have an obligation to maintain the docs, though it would effectively make continued use of newer versions untenable. But pulling existing ones is an unnecessary rug pull when it doesn't cost anything to keep it online. It's a big middle finger to open source.