Request for Community Support and Future Maintenance of MinIO Docker Images

[Kesavaambati]

Hi Team,

We require community support for Docker images and security patches for our MinIO deployment. Previously we used the official minio/minio repository, but it is now in archived state with no future enhancements, support for Helm charts, or Docker image updates.

1. Our infrastructure currently relies on MinIO for object storage
2. We originally cloned and deployed the official minio/minio repository with some customised options.
3. The official MinIO repository was archived on April 25, 2026
4. No future enhancements, security patches, or Docker image updates are available from the upstream project

Current Challenge:

• No official support for Docker image maintenance
• No security patch updates for CVE vulnerabilities
• No Helm chart support or updates
• Production systems require ongoing security maintenance and hardening

Proposed Solution:
We have identified the community-maintained fork https://github.com/pgsty/minio (SILO) as a potential alternative that provides:

• Active community maintenance and support.
• Regular Docker image updates on Docker Hub (pgsty/minio)
• Ongoing security patches and CVE fixes

Request: We seek confirmation and support for:

• Future maintenance and support of Docker images
• Regular security patches and CVE remediation
• Community support channels for technical issues
• Documentation and Helm chart availability
• Long-term project sustainability and roadmap

Expected Outcome: Establish a supported migration path from the archived official MinIO to the community-maintained SILO fork with guaranteed security updates and Docker image maintenance for our production workloads.

Additional informations:
Current docker image we are using - minio:RELEASE.2025-09-07T16-13-09Z
Current charts - minio/minio - https://github.com/minio/minio
Archived by the owner on Apr 25, 2026