· ReadyStack
Worked example
Real numbers from this tool, line by line.
Migrate from MinIO to SeaweedFS: the sample 41-line docker-compose.yml returns 17 findings (1 error, 11 warnings, 5 info) for DevOps, platform and SRE engineers who run MinIO in Docker Compose or Kubernetes.
Why now. MinIO moved from Apache 2.0 to AGPL-3.0 with the commit "update license change for MinIO" on 2021-04-23. The minio/minio GitHub repository is now archived, and its README opens with "THIS REPOSITORY IS NO LONGER MAINTAINED". The community edition is distributed as source code only; the last community release is RELEASE.2025-10-15T17-29-55Z, and the README says legacy binaries will not receive updates. The same README says all usage requires validation against AGPLv3 obligations, including the release of modified code. SeaweedFS is Apache-2.0, and SeaweedFS 4.48 was released on 2026-09-28.
What breaks is the glue around the buckets. SeaweedFS speaks S3, so the SDK calls in your app mostly keep working. The compose file does not. A grep for "minio" matches every line and ranks none, and a chatbot tends to call SeaweedFS a drop-in replacement.
The sample file has one error and it is the image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z. That tag will not be patched. The fix is chrislusf/seaweedfs:4.48 with entrypoint weed and command server -dir=/data -s3, which starts master, volume server, filer and the S3 gateway in one process.
The warnings are the lines that fail quietly after cutover:
- MINIO_ROOT_USER and MINIO_ROOT_PASSWORD: SeaweedFS does not read them. Use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, or an s3.json identity with actions Admin, Read and Write passed as -s3.config.
- "9000:9000": the SeaweedFS S3 gateway listens on 8333. Map 8333:8333 or start with -s3.port=9000.
- --console-address: there is no MinIO Console. weed admin runs the Admin UI on port 23646.
- MINIO_NOTIFY_WEBHOOK_*: SeaweedFS lists GetBucketNotificationConfiguration and PutBucketNotificationConfiguration as not supported. Your thumbnail worker stops getting events. weed filer.meta.tail -pathPrefix=/buckets/uploads is the SeaweedFS way to follow changes.
- MINIO_KMS_KES_ENDPOINT: SeaweedFS SSE-KMS talks to AWS KMS, Google Cloud KMS or OpenBao/Vault, not KES.
- mc admin user add: the MinIO admin API is not there. SeaweedFS implements the IAM API on the S3 endpoint, so aws iam create-user --endpoint-url http://seaweedfs:8333 works.
- mc ilm rule add --transition-days 30: lifecycle configuration is supported, transition rules are not. Keep expiry rules.
The info lines are renames: MINIO_DOMAIN becomes -s3.domainName, /minio/health/live becomes /healthz, and every http://minio:9000 endpoint becomes http://seaweedfs:8333 with path-style addressing.
What the 17 rules cover. Besides the lines above: MinIO source builds (go install github.com/minio/minio, the AGPL path), mc replicate (use weed filer.sync), mc sql and S3 Select, MINIO_IDENTITY_OPENID and LDAP settings (SeaweedFS STS supports AssumeRoleWithWebIdentity and AssumeRoleWithLDAPIdentity), and MinIO disk folders such as .minio.sys, which SeaweedFS cannot read. Copy data through the S3 API with rclone sync instead.
The clean 23-line compose on chrislusf/seaweedfs:4.48 gives 0 findings.
Try it. Paste your docker-compose.yml, Kubernetes manifest or mc script into the free web version at https://getreadystack.com/tools/seaweedfs-migration-lint or install the VS Code extension. Every finding in the open file is free and runs offline. A licence adds one sweep of the whole workspace and a Markdown migration report for the change ticket.
15 seconds — what it actually does
Questions people ask
What does SeaweedFS Migration Lint check in my MinIO files?
It reads docker-compose and Kubernetes YAML, .env files, shell scripts and Dockerfiles line by line against 17 rules and marks every line that ties the setup to MinIO: the minio/minio image, the minio server command, MINIO_* credentials, port 9000, mc admin calls, bucket notifications, replication, lifecycle transitions, S3 Select and KES settings. Each finding names the SeaweedFS fix.
Who is SeaweedFS Migration Lint for?
DevOps, platform and SRE engineers who run MinIO in Docker Compose or Kubernetes and are moving the same S3 store to SeaweedFS, because the minio/minio repository is archived, the last community release is RELEASE.2025-10-15T17-29-55Z, and MinIO is AGPL-3.0. It also suits agencies and MSPs that ship compose files to clients.
Why not just grep for minio or ask a chatbot?
A grep for minio matches every line and ranks none. A chatbot usually says SeaweedFS is a drop-in S3 replacement, but SeaweedFS lists bucket notifications, bucket replication, S3 Select and lifecycle transition rules as not supported, listens on 8333 instead of 9000, and ignores MINIO_ROOT_USER. Those lines fail quietly after cutover.
What is free and what does the licence add?
Free: every finding in the open file, with the line and the SeaweedFS fix, in VS Code and in the web version, offline, no account. The sample 41-line docker-compose.yml gives 17 findings for free. The licence, $29 once, adds a sweep of the whole workspace in one pass and one exported Markdown migration report for the change ticket.
What does the alternative cost?
The MinIO licence question is legal work: DOJ's Fitzpatrick Matrix rates a 15-year litigator at $851/hour for billing year 2026, which is one hour of counsel reading MinIO's AGPL-3.0 obligations. MinIO's own commercial path is AIStor Enterprise, sold by quote only, with no public price.
Ask about this tool
One question, answered by the person who built it. Your email only if you want the answer sent.