If anyone is wondering, the Dockerfile for this repo (thanks for sharing!) basically just copies the binary in, it is a 19 line dockerfile.
I see both sides of the argument here, the people maintaining minio should not have to push docker images for free, it is work to maintain and test, especially across all the host platforms. And, this work isn't that complicated if you want to do it yourself.
>I see both sides of the argument here, the people maintaining minio should not have to push docker images for free, it is work to maintain and test, especially across all the host platforms. And, this work isn't that complicated if you want to do it yourself
I don't. It's automated, it needs approximately zero attention. This is just a company that got where it was benefitting from open source taking the free toys away thinking there'll be profit in it.
I've spent a lot of time trying to get pytorch working inside docker against cuda. That's a big challenge even just on one architecture. It isn't as simple as you make it to be and they have to determine how they allocate resources so they can pay people. I'm still grateful for this project and would rather they dice focus on functionally than packaging.
Building pytorch correctly involves building several python libraries and compiling the extensions in other languages with the correct compiler flags for your particular setup while having a lot of exact version matching software installed at the same time.
Python and pip are just bad at this.
Passing a GPU through into a docker container requires a lot of permissions and flags to be set up just right, and it's way more difficult if your host operating system isn't natively Linux.
What you're describing is essentially the most difficult imaginable container to maintain.
Maintaining a normal containerized application, especially if you want to put it in maintenance mode forever and basically just leave the container working the same way with up to date code... is essentially zero effort. A few hours a year by one person and certainly something open source that a contributor would be happy to be responsible for.
This isn't the case of a company saving money or time by stopping supporting some onerous container build... they're intentionally kneecapping the open source offering hoping more people will pay for their product, which is scummy.
I had positive feelings about minio until I read this, now I don't want to touch it expecting whatever is next to be even more annoying whether I was paying them or not.
I see both sides of the argument here, the people maintaining minio should not have to push docker images for free, it is work to maintain and test, especially across all the host platforms. And, this work isn't that complicated if you want to do it yourself.
https://github.com/golithus/minio-builds/blob/main/Dockerfil...