MinIO stops distributing free Docker images
441–450 of 585 posts
Re: MinIO stops distributing free Docker images
#442Re: MinIO stops distributing free Docker images
#443So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
What alternatives do people recommend that has at least similar features-set and at least similar performance as MinIO?
Re: MinIO stops distributing free Docker images
#444I'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.
> I felt it might be appropriate for me to reach out as one of the stewards of the Docker Official Images program.Re: MinIO stops distributing free Docker images
#445So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
I built my first Slackware box from source. How times changed.
We have a tendency to stick to what we know but everything changes constantly and us being connected amplifies that.
Re: MinIO stops distributing free Docker images
#446Earlier quoted context omitted.
I believe it's too early to judge public adoption. Let's see in a few years if it degrades somehow. For now, they jumped from 55,880 to 56,319 GitHub stars in one day. From the product side, I don't see how this should affect new adopters who didn't read the hn post yesterday
GitHub stars are useless metric.
Re: MinIO stops distributing free Docker images
#447I'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.
Someone seem to already be at it on Discussions https://github.com/minio/minio/discussions/21655 > I felt it might be appropriate for me to reach out as one of the stewards of the Docker Official Images program.
Re: MinIO stops distributing free Docker images
#448I'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.
Someone seem to already be at it on Discussions https://github.com/minio/minio/discussions/21655 > I felt it might be appropriate for me to reach out as one of the stewards of the Docker Official Images program.
The minio image is basically a community one that anyone could have created, but still shows in overall docker hub. It's created by minio themselves. I'm kind of surprised they haven't removed it, but with over a billion downloads they are easily in the top ten of whatever category they fall under creating substantial free advertisement.
Re: MinIO stops distributing free Docker images
#449Earlier quoted context omitted.
I built my first Slackware box from source. How times changed.
Sad to break it to you but it was 30 years ago. We have a tendency to stick to what we know but everything changes constantly and us being connected amplifies that.
Re: MinIO stops distributing free Docker images
#450I'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.
Why is that the best? MinIO is not the type of thing that people ought to be directly making available on the Internet anyway, so CVEs are mostly irrelevant unless you are an organization that has to keep on top of them, in which case you certainly have a process in place to do so already.
People straight pulling an image off Dockerhub (so not a particularly sophisticated use-case) to run seem like they'd be the least likely to be impacted by a CVE like this. The impact is apparently "[it] allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope". Are people pulling from Dockerhub even setting up anything but the absolute most basic (Allow All) ACL?