--- title: "MinIO End of Life: How to Stay Patched and Audit-Ready with Docker ELS" url: https://daily.dev/posts/minio-end-of-life-how-to-stay-patched-and-audit-ready-with-docker-els-ychzc2oun source_url: https://www.docker.com/blog/minio-end-of-life-how-to-stay-patched-and-audit-ready-with-docker-els type: article source: "Docker" published: 2026-08-24T13:02:20.131Z updated: 2026-08-24T13:02:43.142Z tags: ["security", "docker"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # MinIO End of Life: How to Stay Patched and Audit-Ready with Docker ELS **[Docker](https://daily.dev/sources/docker)** · 5 min read · 0 upvotes · 0 comments ## Summary MinIO was archived upstream on February 13, 2026, ending releases, bug fixes, and security patches for a project with over a billion Docker pulls. Docker now offers MinIO as part of its Extended Lifecycle Support (ELS) program, backporting CVE fixes across MinIO and its Go dependency tree, rebuilding hardened images, and shipping SBOMs, VEX statements, and SLSA Build Level 3 provenance for up to five years past end of life. The same ELS coverage extends to other end-of-life software like Nginx, Node, and Python versions, letting teams keep running unsupported components while staying audit-ready and moving migrations onto their own roadmap. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When did MinIO reach end of life and stop receiving updates? The MinIO open-source project was archived upstream on February 13, 2026, meaning it stopped shipping releases, bug fixes, and security patches from that date. The project had surpassed one billion cumulative Docker pulls prior to being archived, so the change affects a very large installed base of production object storage deployments. _Teams tracking end-of-life storage tools can follow patching options for MinIO on daily.dev._ ### What options do teams have if they are still running MinIO after it was archived? Teams running MinIO after its archival have three choices: migrate to a commercial replacement and accept new licensing and lock-in, take on staffing an in-house Go security engineering effort to patch it themselves, or pay a vendor to maintain and patch the existing MinIO deployment. Doing nothing is explicitly not a viable fourth option because new CVEs arrive with no upstream fix. _Comparing migration versus vendor-supported patching paths is easier with daily.dev tracking storage infrastructure news._ ### What does Docker's Extended Lifecycle Support (ELS) provide for end-of-life software like MinIO? Docker ELS builds and maintains hardened images for software after its upstream end of life, for up to five years, patching critical and high-severity CVEs on a 14-day SLA. It covers MinIO and its full Go dependency graph including transitive dependencies, and ships each image with SBOMs, VEX statements, and SLSA Build Level 3 provenance as audit evidence. _daily.dev helps engineers stay current on vendor patching options for aging infrastructure dependencies._ ## Similar posts on daily.dev - [MinIO Is Dead, Long Live MinIO](https://daily.dev/posts/minio-is-dead-long-live-minio-ovpwwbf7s) · Hacker News · 109 upvotes · 9 comments - [MinIO Is Done With Open Source, What Are Your Options?](https://daily.dev/posts/minio-is-done-with-open-source-what-are-your-options--wzuzouq5b) · It's Foss · 0 upvotes · 0 comments - [Docker release? · Issue \#21647 · minio](https://daily.dev/posts/docker-release-issue-21647-minio-nrflj57p7) · Hacker News · 19 upvotes · 3 comments --- Tags: [#security](https://daily.dev/tags/security), [#docker](https://daily.dev/tags/docker) [View this post on daily.dev](https://daily.dev/posts/minio-end-of-life-how-to-stay-patched-and-audit-ready-with-docker-els-ychzc2oun)