Live data from Hacker News

MinIO stops distributing free Docker images

github.com

141–150 of 585 posts

Re: MinIO stops distributing free Docker images

#141
post #88
post #33

Earlier quoted context omitted.

Afaik Ceph has its own object-storage functionality as well, which seems to be S3-compatible: https://docs.ceph.com/en/latest/radosgw/#object-gateway

I believe you're forced to have your data backed by a Ceph OSD. Whereas Minio can point to an NFS share on a NAS.

> I believe you're forced to have your data backed by a Ceph OSD.

It makes perfect sense as this is a feature of Ceph.

> Whereas Minio can point to an NFS share on a NAS.

Eh, different trade-offs.

Re: MinIO stops distributing free Docker images

#142
post #76

Earlier quoted context omitted.

There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. Building minio is not only trivial, but is standard procedure - the latest release is in my distributions standard package repo, and they would not use prebuilt binaries. If you want that dockerized, the…

> There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. Agree. But that's not my point. If you start an oss project from scratch and you don't want to provide builds that's fine. If you start your oss project, provide public docker images since the beginnin…

It is also not irresponsible, or a rug pull. The project is still available, free, and widely packaged as it always has been, just one redundant source removed.

I don't get why one they would provide prebuilt binaries in the first place, and removing them is just cleanup.

Re: MinIO stops distributing free Docker images

#143
post #49

The title of the HN submission might look a bit misleading. It's easy to misinterpret it and think MinIO stops being open source (which would be a bigger deal IMHO). I think this would be better: "MinIO stops distributing free Docker images" --- See also the relevant README section: https://github.com/minio/minio?tab=readme-ov-file#source-onl...

That was my interpretation of the title when I first clicked it. Still interesting but easy to misunderstand nevertheless.

Re: MinIO stops distributing free Docker images

#144
post #127

Earlier quoted context omitted.

> When you always published and built Docker images for the public you are creating an expectation That expectation does not entitle anybody to anything though. > people will rely on that and will chose your software based on that expectation That is their decision. Without any contract or promise, there is no obligation to anybody. > You suddenly deciding that you won't be offering updated Docker images […] is appro…

> Without any contract or promise, there is no obligation to anybody. When a restaurant which you've been going to for years one day decides to serve you your favorite meal with a bit of poop on the side, do you not have the right to be upset about it? They're not under any obligation to serve you meals you're happy with. There was no contract or promise. The fact you're paying for their service doesn't buy you these…

> If you want to place restrictions on how your software is used and who gets to enjoy it, that's fine, but make those terms explicit by choosing the appropriate license and business model from the start. Stop abusing OSS as a marketing tactic.

But MinIO didn't do any of that. They're still a 100% open-source project, with the proper license.

Re: MinIO stops distributing free Docker images

#145
post #101

Earlier quoted context omitted.

There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. Building minio is not only trivial, but is standard procedure - the latest release is in my distributions standard package repo, and they would not use prebuilt binaries. If you want that dockerized, the…

> I can't stand the entitlement people (everyone, not one particular person) feel when they are provided things for free. Does it make you less frustrated to remember that humans are pattern recognition machines and our existence is essentially recognising and adapting to patterns, and so when someone does something repeatedly - regardless of if they're doing it for free - humans will recognise a pattern and adapt to…

Funny that pattern recognition does not extend to the universal pattern of "things end". A stoic would be appalled--if they'd care.

Re: MinIO stops distributing free Docker images

#146

Earlier quoted context omitted.

There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. Building minio is not only trivial, but is standard procedure - the latest release is in my distributions standard package repo, and they would not use prebuilt binaries. If you want that dockerized, the…

If it were for a feature request, it would feel more justified. People feeling entitled to making feature requests is one thing. Like they can get fucked. Contribute code or pay me. But if I let something loose out into the world that suddenly started causing problems because someone discovered you could stab people with it, I'd be going around making sure all of the copies I gave out it had a knife guard put in plac…

We're not going around making kitchen knives illegal. I would go out of my way to mitigate footguns where an entirely legitimate use or legitimate source of confusion would turn foul, but if you chose to go out of your way to misuse it as a hammer or ignore documentation, then you're on your own.

In this case, we're not even talking about that though, it's just a redundant prebuilt binary getting janked. I don't think it makes sense to provide prebuild binaries in the first place.

Re: MinIO stops distributing free Docker images

#147
Lots of people in this thread keep repeating the idea that, "Nobody owes anybody anything".

Sure, just like nobody owes minio goodwill or business. People sour on these kinds of things because they feel sneaky and backhanded. It tells you something about the kind of people you're working with.

Imagine if a food kitchen suddenly started charging for the food, without notice. Or they started charging to use changing rooms in clothing stores. Etc, etc. You'd, rightly, expect a negative reaction, even if the "food kitchen doesn't owe anybody anything".

The biggest misstep in these situations is the corporations avoiding being honest and communicative about why the changes are suddenly necessary. We all know, intuitively, that in most cases its because it's not for a good reason. It's because they are greedy or otherwise feel pressured to show infinite growth.

Re: MinIO stops distributing free Docker images

#148
I think Minio is the only Go client for S3 API and S3-compatible APIs. I cannot say I liked using it, but I had no choice. Nowadays I run my own file storage with my own API, so I no longer care.

But if anyone wants to run their own file storage(so not a client), there is https://github.com/seaweedfs/seaweedfs

Re: MinIO stops distributing free Docker images

#149
post #127

Earlier quoted context omitted.

> When you always published and built Docker images for the public you are creating an expectation That expectation does not entitle anybody to anything though. > people will rely on that and will chose your software based on that expectation That is their decision. Without any contract or promise, there is no obligation to anybody. > You suddenly deciding that you won't be offering updated Docker images […] is appro…

> Without any contract or promise, there is no obligation to anybody. When a restaurant which you've been going to for years one day decides to serve you your favorite meal with a bit of poop on the side, do you not have the right to be upset about it? They're not under any obligation to serve you meals you're happy with. There was no contract or promise. The fact you're paying for their service doesn't buy you these…

> The fact you're paying for their service doesn't buy you these rights either.

It certainly does. In the UK and many other countries (possibly not the US), as soon as you are paying for a good or service you are entitled that it is satisfactory quality, fit for purpose and as described. I think it's uncontentious that a meal at a restaurant that includes poo is not satisfactory quality. Businesses have less rights than consumers but this would still count. However, the restaurant is certainly free to refuse serving you at all (unless they're it's because of a protected characteristic e.g. because of your race or gender).

I'm not sure how much that affects your analogy since it was probably a bit too far removed from the original situation to be useful anyway.

Re: MinIO stops distributing free Docker images

#150
post #112

Earlier quoted context omitted.

Hey, tone down, please. Also, have you, for some reason, totally missed the first point in my comment? > Do you know their reasons for discontinuing? Are you even entitled to know that? It's their private matter. Fully addressed in the "if you can help it" part of my comment. > You have no idea how entitled you behave. I have 100% idea how entitled I behave. I don't at all. I don't use MinIO. As an employee, I push i…

If you were relying on their pre-built binaries, you presumably still have them. It's not like they went and deleted them off of your computer. They're just not giving you new pre-built binaries (but they're still giving you new code for free! And others pre-build binaries for free anyway). Do the old ones stop working at some point? Note that a CVE is not an indication that something doesn't work. In the real world,…

Existing binaries don't stop working, but adapting your infra to get the update can take some time.

Without other elements, it's definitely not nice to stop releasing the binaries out of the blue, especially for a security fix. To me it's purely a question of breaking expectations you've built yourself (I don't mean entitlement, I mean expectations).

Now, it's indeed not the end of the world, and:

> you have no one to blame but yourself if you rely on others' charity to meet that obligation

100% agree with you on this (that's my first point in my original comment).

Post reply on HN