Evidence note: This article rests on two kinds of evidence. The core facts about MinIO’s end-of-life date and the terms of Docker Extended Lifecycle Support come from Docker’s own announcement, a primary vendor source, and are attributed as such throughout. The history of the free edition’s web console comes from a Hacker News discussion and has not been independently corroborated. No independent third-party confirmation of either the EOL date or the ELS terms was found for this article; where that matters, the text says so.
MinIO reached end of life in February 2026
According to Docker’s announcement, MinIO reached end of life in February 2026, meaning upstream no longer ships security patches or maintenance releases for the object store (Docker blog). The date itself is stated by Docker, a vendor with a commercial product built around that exact situation, and no separate confirmation from MinIO’s own project channels was reviewed here. Readers who need the date for compliance paperwork should verify it against MinIO’s release history directly.
For self-hosters the practical consequence is straightforward. An S3-compatible object store that sits behind a home lab, a local AI pipeline, or a small team’s backup system does not stop working when it goes end of life. It stops receiving fixes. Any vulnerability disclosed after the cutoff stays open on every instance still running the last release.
Before EOL: the web console was removed from the free edition
The end-of-life notice did not arrive out of nowhere. Commenters in the Hacker News thread attached to a Show HN post for Sairo, an alternative tool, describe MinIO having removed its web console from the free edition in the year before that post. This claim comes from forum participants rather than from MinIO release notes, and it has not been cross-checked for this article. The direction of travel it describes, a community edition losing features that stay in the commercial tier, is consistent with the later EOL but should be treated as a reported recollection rather than a verified timeline.
If accurate, it explains part of the sentiment visible in that thread. Users who had already lost the browser-based admin interface were then told the software itself would stop being maintained. Whether the console removal was a deliberate prelude to the EOL, or an unrelated product decision, is not something the available sources settle.
What Docker Extended Lifecycle Support is
Docker’s answer is a paid program called Extended Lifecycle Support, or ELS. According to Docker’s announcement, ELS keeps end-of-life software such as MinIO patched, compliant, and audit-ready for up to five years (Docker blog). The "up to five years" figure is Docker’s own stated ceiling, not a guarantee any independent party has tested, and the announcement does not spell out what conditions might shorten it for a given project.
The three words Docker uses deserve unpacking. "Patched" means Docker backports security fixes to a version upstream has abandoned. "Compliant" and "audit-ready" point at the real buyer: organisations whose auditors will flag an unsupported component regardless of whether it has a known exploit. For those teams, the value is less about any specific CVE and more about being able to show a support contract when asked.
ELS coverage scope: from individual versions to entire projects
Docker states that ELS coverage ranges from individual versions that upstream no longer supports up to entire projects (Docker blog). In practice that describes two different situations. The first is a project that is still alive upstream but where a team is pinned to an old release it cannot easily upgrade past. The second is a project like MinIO where upstream itself has stopped, and the entire codebase needs a caretaker.
The announcement does not, as far as the reviewed text shows, publish pricing, list which MinIO versions are covered, or say whether coverage includes the removed console. Those are the details a self-hoster would need before treating ELS as a plan rather than an option.
What this means for teams still running MinIO in local AI and self-hosted stacks
MinIO has been a common choice for local AI setups because model artefacts, datasets, and vector store snapshots all want an S3-compatible target that runs on one machine. Teams in that position now face three paths. They can keep running the final release unpatched and accept the exposure, which is defensible only for a store that is never reachable from outside a trusted network. They can migrate to another S3-compatible store, which is the path most home-lab users in the Hacker News discussion appear to be weighing. Or they can buy ELS, which mainly suits teams with compliance obligations rather than hobbyists.
For readers already planning a migration off end-of-life infrastructure, the same questions came up when a container registry shut down earlier this year; see the migration path to Docker Hardened Images for how that one played out. The earlier piece on the MinIO end-of-life notice itself covers the initial announcement in more detail.
One caution for the migration route: "S3-compatible" is a spectrum. Tooling that relied on MinIO-specific behaviour, such as its bucket notification setup or its particular handling of multipart uploads, may need adjustment on a replacement store. Nothing in the sources quantifies how common that is, so a test migration on a copy of the data is the safe first step.
Open questions the announcements do not answer
Several points remain open on the evidence reviewed here:
- Independent confirmation of the EOL date. The February 2026 date is stated by Docker. No MinIO-authored notice was checked for this article, so the date rests on a single vendor source.
- ELS pricing and eligibility. Docker’s announcement describes what ELS does but the reviewed text does not state what it costs or whether individuals can buy it.
- What "up to five years" depends on. The ceiling is stated; the conditions that would shorten it are not.
- The console timeline. Whether and when the web console left the free edition is reported in a forum thread, not confirmed by release notes.
- Coverage of MinIO forks. The sources do not say whether community forks of the last release fall inside or outside ELS scope.
Until MinIO’s own channels or a second independent source address these, the safest reading is that Docker has announced a support offering for a product it says is now unmaintained, and that the details a self-hoster would need to act on it are still thin.