ker release?

TL;DR

If it isn’t, can you please push a new release for this installation method? If you install via Docker or quay.io images, build the container yourself from source; see the 'source-only distribution' section of the MinIO README.

Steps

1. What was reported:

Issue minio/minio#21647 (closed, 41 comments): Hello,

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

MinIO no longer publishes container images for new releases (including security releases). The project is now a source-only distribution. If you install via Docker or quay.io images, build the container yourself from source; see the 'source-only distribution' section of the MinIO README. Maintainer-confirmed.

When to use

You are seeing this: What was reported: Issue minio/minio#21647 (closed, 41 comments): 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. Use this skill when you run into "ker release?".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the GitHub issue, the reporter asked: ker release?. The working answer that came out of the thread: MinIO no longer publishes container images for new releases (including security releases). The project is now a source-only distribution. If you install via Docker or quay.io images, build the container yourself from source; see the 'source-only distribution' section of the MinIO README. Maintainer-confirmed. Source: https://github.com/minio/minio/issues/21647