Docker release?

[neil-lcv-cs]

Hello,

I did not find a new image for the security release Security/CVE RELEASE.2025-10-15T17-29-55Z, on quay.io nor DockerHub.

Is it expected? If it isn’t, can you please push a new release for this installation method?

Thank you.

[harshavardhana]

This project is a source only distribution now, if you want to build containers you need to build them yourselves

https://github.com/minio/minio?tab=readme-ov-file#source-only-distribution

[neil-lcv-cs]

Wait… are you really giving up on your 1-billion+ downloads Minio Docker image?
You most certainly have your own reasons, though I can’t understand why someone thought it would be beneficial for your company to abandon such a popular distribution.

Was there an announcement prior to the release?
Also the timing is pretty bad… You could’ve waited for a bugfix release or a feature release, but doing that move on a severe security release without warning is kinda harsh…

Anyway, thanks for all the fish, time to fork and build.

[harshavardhana]

Wait… are you really giving up on your 1-billion+ downloads Minio Docker image? You most certainly have your own reasons, though I can’t understand why someone thought it would be beneficial for your company to abandon such a popular distribution.

Was there an announcement prior to the release? Also the timing is pretty bad… You could’ve waited for a bugfix release or a feature release, but doing that move on a severe security release without warning is kinda harsh…

This decision was done prior to the CVE. It is just unfortunate timing.

Anyway, thanks for all the fish, time to fork and build.

[sathieu]

You are joking ?!

The commit about source only is 4 days old (9e49d5e)

We are currently paying for a license while using the open source version, you already removed the oidc code from UI console and now docker images. We are not happy by this lock-in. We will discuss this internally, but you may loose a paying customer with this behavior.

[ondrejmo]

I think that after this issue and https://github.com/minio/object-browser/issues/3546, this project and it's maintainers can no longer be trusted not to do another rug pull. Sad to see it all go, because I used it and frequently recommended it over the last 6 years.

[davinkevin]

Just 😮…

[BloodyIron]

It's as if the decision makers never heard of the ownCloud -> nextCloud migration... or countless others. Oh well, another will come and replace MinIO.

I'd also like to point out this makes the internet less secure because MinIO systems in-place in many instances will not get updated, not only for the latest CVE but for future CVEs.

[PrivateGER]

Fascinating. What an utterly untrustworthy move.

Willingly letting people run outdated versions of your software because you can't be bothered with the CI or just really hate community users is crazy.

[YannBirba]

Wtf is happening here... ?