Tried starting an older Laravel Sail project, but pulling
minio/minio:latest failed.
Turns out Sail removed MinIO support in PR #899 and now offers RustFS instead.
I tried replacing MinIO with Silo (pgsty/silo), a MinIO fork. It worked with the existing service name and environment variables, and basic S3 operations passed.
Laravel Storage integration and migration of existing MinIO data are still untested.
I'm considering proposing Silo as an optional Sail service for existing MinIO users. Would the migration benefits justify the additional maintenance burden?
Sail PR #899:
https://github.com/laravel/sail/pull/899GitHubRemove the MinIO service stub by nbayramberdiyev · Pull Request #899 · laravel/sailMinIO's community edition has been discontinued. The GitHub repository was archived in April 2026, and the images were removed from Docker Hub. This means selecting the minio service during sai...
commit 7f7cb1b
I just discovered that MinIO is no longer resolving (https://dev-null.sh/@shane-smith/commits/01a1d61b-60f8-72d5-bbf3-18c6b5a1bf23) and this came up as a related commit.
You mentioned that Laravel Sail now offers RustFS instead.
So with that in mind, what made you use Silo over…
/dev/nullShane Smith (@shane-smith) on /dev/null: “MinIO is no longer open source. What are you using instead for a local…”MinIO is no longer open source. What are you using instead for a local S3-compatible data store? It looks like alternatives are Garage, SeaweedFS, and RustFS. Can someone give me a recommendation?