Live data from Hacker News

MinIO stops distributing free Docker images

github.com

511–520 of 585 posts

Re: MinIO stops distributing free Docker images

#511

I'll let docker's security team know that an insecure, obsolete docker image is being served and the maintainers have officially acknowledged they will no longer support it. Best to get insecure and vulnerable software out of the hands of those who may not be familiar with this CVE or their change in policy that has not gotten a press release in any way.

Imagine the absolute chaos if docker would do that, pull vulnerable images offline. Not a single company would be able to build their software anymore.

Actually, Docker did something like that, where they limited the amount of docker images they would host for you for free to a reasonable number. The result was pretty similar to this current outcry: https://news.ycombinator.com/item?id=24143588

Re: MinIO stops distributing free Docker images

#512
post #482

Earlier quoted context omitted.

...Or just spend 10 minutes and familiarise yourself with the basic docker build command? Its really dead simple.

Then you have to maintain a pipline and registry just to fix something that should be fixed upstream?

The fix is upstream, they're giving away the patch for free.

Setting up a registry and a pipeline is annoying but it's hardly a life changing event. It's certainly easier than migrating to a competitor.

Re: MinIO stops distributing free Docker images

#513

So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.

It's still free and available, you just need to run the docker build command yourself or pay them to get their enterprise version.

Well, you can build some parts of it, but the builds aren't the only thing they're removing. Reading some of the Github issues, eg. https://github.com/minio/object-browser/issues/3546:

> We initially explored a basic admin UI for the community branch but haven't actively maintained it. Building and supporting separate graphical consoles for the community and commercial branches is substantial. Honestly, it is hard to duplicate this work for the community branch. A whole team is involved in console development, including design, UX, front-end, back-end, and pen testing. This commit introduces an enhanced object browser but removes the unmaintained admin UI code.

They deleted the admin UI from the current version of the open-source side. It's time to pay the VCs, the project is being rug-pulled and they're going all in on the enterprise version.

Re: MinIO stops distributing free Docker images

#514
What makes me sad is that, as mentioned in other threads, this destruction in reputation could've totally been avoidable. If MinIO had took the time to give out warnings months in advance and help community members (or even other companies) to host the Docker builds somewhere else, there would've be close to none backlash. Yet they've decided to make it such an abrupt transition and especially when a CVE is involved.

Re: MinIO stops distributing free Docker images

#515
post #469

It is unfortunate, but somewhere you need to draw the line, if you are planning to stop releases. If they fix this, how about the next? Why fix this one but not the next CVE? Is the reaction same next time and they end up fixing endlessly?

IMO they should've waited at least a month after updating their README. The timeline is rather short.

It'll be hard to convince people to buy their commercial offering after pulling something like this.

On the other hand, they did the work for free, so it's up to them to decide when to stop doing that. Plus, anyone can fork the repo and maintain their own version with fixes and docker images and everything.

Re: MinIO stops distributing free Docker images

#516

Earlier quoted context omitted.

If you use this tech, perhaps you could explain what the real issue is behind dropping Docker? I mean, it's still AGPL licensed — why can't you use it from source? In other words, what is the significant difference for your team that's worth changing the stack and navigating through the uncertainty of an alternative product?

Part of it is the trend of MinIO walking away from community customers. That to me is not a good sign, especially when it comes to project longevity. Do projects that do this kind of thing continue to flourish and thrive? I'm not sure that they do. It's hard to feel good about remaining hitched to a horse that continues to send out red flags, especially when there are other good options out there for us.

Thanks, so the reason is that you are not confident in this open-source offering anymore.

Re: MinIO stops distributing free Docker images

#517
post #482

Earlier quoted context omitted.

...Or just spend 10 minutes and familiarise yourself with the basic docker build command? Its really dead simple.

Then you have to maintain a pipline and registry just to fix something that should be fixed upstream?

Again folks, you don´t "fix" anything by building a docker image. The fix is already in the source, you just need to run one command to build the image. The registry is something you should have in your infrastructure, if you are at least half-way seriously doing anything in the domain of containers and Kubernetes. But if you dont have one, it seems you are running things locally, for your toy project.Well then, just in that case just deploy from your local docker cache. All of this is actually merely a couple of commands in your simplified use-case.

Re: MinIO stops distributing free Docker images

#518

Earlier quoted context omitted.

Ease of setup and certified working solution. And yes, people should pay for certified working solution. But not when they use it the first time itself

Yes, I understand that Docker is easy to set up. However, I also understand that for any organization it is very painful to change their existing stack, thus I'm trying to understand what is gained between AGPL sources without Docker and switching technology to something different with Docker except 'ease of setup'.

A lot of small shops will find it easier to shift to a compatible S3 object storage which have their own docker compse scripts up and running than figure out how to build minio images successfully. Most products nowadays gives you ansible and docker scripts which can get you up and running inside an hour and then you can configure stuff later.

Building something on your own on the other hand is probably easily a half-time engineer just for build quality and dependency tracking.

Huge number of MinIO shops is one head node and 7 jbods in a single rack (giving you more thsn 10PB). And two such racks for redundancy and one offside rack for backup.

Re: MinIO stops distributing free Docker images

#520

what a terrible turn ... screw 'em so what're you folks moving to? spinning up a local minio instance was what I always sprung for when doing local testing of s3 things... Edit: 9.4k stars. Looks compelling. https://github.com/rustfs/rustfs

We'll just build our own docker image, it's not a huge task
Post reply on HN