←back to thread

672 points LexSiga | 1 comments | | HN request time: 0s | source
Show context
adamcharnock ◴[] No.45667316[source]
We [0] use MinIO with for our clients so we've just thrown together a nightly build process. Use/fork as you wish:

https://github.com/golithus/minio-builds

Example use:

    docker run -p 9000:9000 -p 9001:9001 ghcr.io/golithus/minio:latest

[0]: https://lithus.eu
replies(2): >>45669177 #>>45674234 #
xrd ◴[] No.45669177[source]
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.

https://github.com/golithus/minio-builds/blob/main/Dockerfil...

replies(2): >>45669283 #>>45670189 #
colechristensen ◴[] No.45670189[source]
>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.

replies(1): >>45676895 #
1. xrd ◴[] No.45676895[source]
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.