Pain Points of Alternatives to Single-Node Local S3
Problem
Users need an alternative to single-node local S3 that is easier to deploy and automate than MinIO, with reliable security patches; current options either lack automated initialization or require tedious manual setup.
Pain points
- Lack of a trustworthy maintenance branch for MinIO that addresses stability and CVE patching.
- Deploying Garage in a single-node setup requires manual bucket, key, and permission configuration, and its Docker image isn’t auto-created.
- Absence of a solution that can automatically initialize and provide out-of-the-box S3-compatible storage.
- Shortcomings compared to projects like Versity GW, hs5, and SeaweedFS in terms of feature completeness and ease of use.
Questions to verify
- Have you encountered issues with MinIO’s complex configuration or lack of automated initialization in real projects?
- Do you prefer using existing open-source projects (e.g., Garage, hs5) rather than maintaining your own patch branch?
- Would you benefit from a Docker image that can automatically create buckets, keys, and permissions to simplify deployment?
Evidence
quote
Ruohang Feng has forked MinIO to pgsty/minio and is promising to maintain a stable, CVE-patched, distribution.This is what I went with.I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints. Given the fork's maintainer puts their real name on it & stakes their reputation, you'd assume it can be trusted - but my use case is simpler than most.
quote
garage server --single-node --default-bucket
quote
Doing that the first time manually was annoying, but their docs are pretty nice and an AI agent can build you your own Docker image with custom init in about 15 minutes.
quote
My https://github.com/uroni/hs5 is designed for this use case.One notable thing is that compared to MinIO (and others) it does not store the objects as individual files.
fact
Garage added an automatic configuration feature in v2.3.0 that makes it easier to set up single nodes:
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.