The bex.co blog recounts that MinIO removed the minio/minio and minio/mc container images from Docker Hub between September 11 and 14, 2026, so fresh CI runners and new machines can no longer pull the object-storage server while only warm layer caches keep working, breaking the Docker Compose workflow many projects relied on for S3-compatible test storage. It frames the deletion as the last step of a retreat from community distribution that began with the 2021 relicensing from Apache 2.0 to AGPLv3, continued with the removal of the admin console from the community edition in May 2025 and the end of free binaries in October 2025, and ended with the repository being archived in April 2026, leaving the server code AGPLv3 and forkable but without new releases or reviewed security patches. MinIO instead directs users to its commercial AIStor product, and the article warns that repointing builds at quay.io freezes a year-old, unpatchable release in place.
MinIO deletes its community container images from Docker Hub
The bex.co blog recounts that MinIO removed the minio/minio and minio/mc container images from Docker Hub between September 11 and 14, 2026, so fresh CI runners and new machines can no longer pull the object-storage server while only warm layer caches keep working, breaking the Docker Compose workflow many projects relied on for S3-compatible test storage. It frames the deletion as the last step of a retreat from community distribution that began with the 2021 relicensing from Apache 2.0 to AGPLv3, continued with the removal of the admin console from the community edition in May 2025 and the end of free binaries in October 2025, and ended with the repository being archived in April 2026, leaving the server code AGPLv3 and forkable but without new releases or reviewed security patches. MinIO instead directs users to its commercial AIStor product, and the article warns that repointing builds at quay.io freezes a year-old, unpatchable release in place.
Source: Bex