MinIO
futomaki.minio
A Docker Compose file for MinIO alone, generated from the catalog and checked by the safety inspector. No account needed.
Object storage server with an S3-compatible API for on-premises and edge deployments, providing erasure coding, object versioning, write-once retention locks and bucket replication.
MinIO presents buckets and objects over the S3 API, so SDKs, command-line tools and applications written against S3 work against it unmodified. A distributed deployment spreads objects across drives and nodes with erasure coding and tolerates disk or node loss up to the configured parity, while a single-node deployment covers development and smaller workloads. Server-side features include versioning, retention locks, lifecycle expiry rules and replication between clusters. A first deployment creates a bucket, uploads an object with an S3 client and reads it back with a matching checksum.
You know it worked when
- The server starts and reports its drives online.
- An S3 client authenticates with the configured credentials.
- A bucket can be created and an object uploaded into it.
- The same object downloads intact and its checksum matches.
- Objects survive a container restart with the data directory persisted.
Known sharp edges
- Root credentials come from environment variables and placeholder values are accepted without complaint, leaving the whole store open to anyone who can reach the port.
- Erasure coding and its parity are fixed when the deployment is created, so changing drive layout later means standing up a new deployment and migrating.
- Recent community releases have reduced the built-in web console to object browsing, moving administration to the command-line client.
- The API and console listen on separate ports and exposing the wrong one through a reverse proxy is a common misconfiguration.