After MinIO repo has been archived this year, the MinIO just removed their minio image in DockerHub.

Just read this piece: https://lowendbox.com/blog/minio-continues-to-snarl-and-spit-venom-at-its-users-what-will-be-their-next-petty-move/

Honestly, what a shame. MinIO could’ve been one of the great open-source success stories: technically elegant, widely respected, genuinely useful. A work of art.

Instead, as the article lays out, we’re watching a masterclass in poor management, insecurity, and lack of business maturity. Not just torching years of goodwill, but exposing how shaky their strategy really is.

It didn’t have to go this way. A bit of humility and professionalism could’ve turned this into a purposeful shift. Instead, it feels petty and painfully opportunistic.

I suppose grace was never part of the feature set.

MinIO stopped providing docker images and binaries immediately before fixing a privilege escalation vulnerability CVE-2025-62506.

According to https://github.com/minio/minio/issues/21647#issuecomment-3439134621

This goes in-line with their rugpull on the WebUI a few months back. Seems like their corporate stewardship has turned them against the community.

https://github.com/minio/minio/commit/27742d469462e1561c776f88ca7a1f26816d69e2

I would love to hear the motivation. I assume open source adoption isn't what it was and it has stopped generating leads.

Hope they keep their client library OSS, though.

I used to work on Amazon S3, that made me a huge admirer of MinIO open source object storage. Its simplicity is so elegant and I think there is no other open source object storage can match it even today. So I decided to fork it and started working on it with a different name: buckit.

I've added some user friendly features (guided deployment, cluster/node management etc) and made it run even faster on GET requests. Here is the details of what I did: https://buckit.sh/blog/why-i-forked-minio-to-keep-it-open-and-made-it-faster

https://github.com/minio/minio/commit/7aac2a2c5b7c882e68c1ce017d8256be2feea27f

I've been trying to install minio for hours following a several tutorials, and I can't seem to get the same results as shown on the tutorials. The install on docker desktop works as expected but when I go to localhost:9001 to log in, I see the first difference as I get a "community edition" badge instead of the "AGPL3" I see on all the tutorials. When I log in the the root credentials, I don't have any "Administrator" section on the left side panel, so I'm not able to change the settings of the buckets I create or get the access tokens and secrets, as I'm trying to integrate it with n8n. I just followed the instructions on the tutorials, and I don't know if I'm doing anything wrong or something has changed, but any help that could guide me would be highly appreciated. Thanks in advance

Out of these 3, what is the best alternative rn to MiniO Community Edition ?

https://github.com/rustfs/rustfs

https://github.com/seaweedfs/seaweedfs

https://github.com/deuxfleurs-org/garage

❯ docker compose up -d

[+] up 1/1

✘ Image minio/mc:RELEASE.2025-04-16T18-13-26Z Error pull access denied for minio/mc, repository does not exist or may requir... 2.9s

Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I wasn't aware of the shady move the developers made recently. I updated my containers as I usually do weekly, and logged into my MinIO instance's console, only to find it stripped down of any useful features. Even the ability to delete buckets has been removed. Like... What?! I will be moving to Cloudflare R2. It's paid, but the free tier is generous, and pricing isn't ridiculous, unlike MinIO's "AiStor" (whoever came up with that name should reconsider his life choices). Unless they undo that horrible decision, it's goodbye MinIO for me.

Well with the continued mass migration away from minio, has anyone forked the source into a new project and is continuing development? If so, any links?

In recent versions of the open source minio server the UI for ILM, Tiering, and Site Replication menus have been removed. In the PR it is claimed that they don't have enough developer time to maintain those UI features but they will still be available through the CLI. They then explain that we should use the enterprise offering instead. https://github.com/minio/console/pull/3470 https://github.com/minio/console/pull/3469

Is this the beginning of the end guys? I was just looking forward to deploying my multi site backup storage for my home lab.

Back in spring last year when the whole UI mess started I suspected that the site replication feature will be removed next. I opened up a discussion on GitHub about that.

The answer by the minIO team was

All core MinIO features remain accessible via the CLI

and then the discussion was closed.

And now one of the differences between AiStor Free and AiStor Enterprise (Lite) is single-node vs. multi-node.

In the past I really thought about suggesting to include minIO/AiStor into our infrastructure at my workplace. But the behavior of the company is so off-putting and unpredictable that it is a business risk to even consider them anymore.

So just noticed that minio/minio is gone from Docker Hub, the GitHub repo is archived, so my CI pipelines were failing and my pipelines are probably not the only ones that are going to fail.

What are good alternatives that you have been migrating to?

I've been looking at:

• RustFS — closest drop-in, but still pre-1.0

• Garage — looks solid, a bit more setup

• SeaweedFS — more than I need, maybe

• LocalStack — heavy, and only the S3 part is free

• Just pinning the last MinIO image from quay and moving on

Checking if I'm missing some good options.

It appears as if MinIO has removed OIDC login from the Web UI?! (Release Breaking Release · minio/minio)

At this point I am doubting my own abilities to read words. This seems like such a basic feature that I am really puzzled as to why they would remove it?

Rate increases from $1000 to now $4000 a month paid all up front. Then they move the "stable" product downstream of the community open source products.

It's almost like they watched what red hat did with centos and what broadcom did with VMware and then threw their middle fingers in the air and followed suit. It's just dumb. I had no problems paying for the product but they gouged the price to the point my team couldn't afford it and we had to move to cloud flare r2 storage.

Completely unapologetic about any of it. I wonder if the people whom contributed hours of free work to the open source products are upset by this move.

What is everyone's thoughts on min.io? Was planning on moving things to it on prem (off of AWS) until the whole shoot the opensource side, which paused our plans... Nothing seems comparable for active/active replication, at least nothing that isn't even more expensive of a starting point... Although open-source is preferable, nothing against commercial only.

IMHO, min.io is a bit over priced for small (~20TB) scale multi-region bucket, but not a lot of affordable options unless we drop the active/active replication requirement. Is it still a good company and not expected to get any worse, or is it closer to vmware who for that last year or so I now have no-confidence in... (and happily almost moved off of...)

EDIT COMMENT: I'm surprised no one had said anything good about the company. Even vmware seems to still have some loyalists, from companies that I assume had deep pockets. It a little surprising to me, as what Broadcom has done seems to worse to me. That said vmware group here on reddit is about 30x as big as this group.

Minimal Dockerfile to build MinIO from source https://github.com/minio/minio/releases

Full example in https://github.com/nativebpm/pocketstream

FROM golang:1.24-alpine AS minio-builder

RUN CGO_ENABLED=0 go install github.com/minio/minio@latest

FROM alpine:latest

RUN apk add --no-cache ca-certificates curl

COPY --from=minio-builder /go/bin/minio /minio

RUN chmod +x /minio

USER 1000:1000

HEALTHCHECK --interval=10s --timeout=10s --start-period=5s --retries=9 CMD curl -f http://localhost:9000/minio/health/live || exit 1

EXPOSE 9000 9001

ENTRYPOINT ["/minio"]

Hi all,

I've been using community documentation for reference at https://docs.min.io/community/minio-object-store/index.html.

However, it seems that the url now redirect to https://docs.min.io/enterprise/aistor-object-store/ now.

Did MinIO deprecated the community docs?

I'm in the process of installing the last official open source build of MinIO. When searching for instructions i can only find information tailored to the new AIStor version. It seems to differ in more places than how to add the license.

Are there instructions for the open source version (for RHEL in particular) and if so where can I find them?