Docs Blog Download & Install About 简体中文 GitHub · 1.9k

01 / DATA SERVICE

SILO Server

From local validation to a multi-node production cluster, choose the delivery path that matches your control boundary.

CURRENT VERSION 2026-06-18 Release notes & all artifacts ↗
CONTAINER / MULTI-ARCH

Run a persistent instance in minutes

linux/amd64linux/arm64DockerPodman

Best for local evaluation, development, and deployments that already use containers as the delivery boundary. Pin the image tag, replace credentials, and use persistent storage in production.

shell
docker pull pgsty/minio:latest
docker run -d --name silo --restart unless-stopped \
  -p 9000:9000 -p 9001:9001 \
  -v /data/minio:/data \
  -e MINIO_ROOT_USER=silo-admin \
  -e MINIO_ROOT_PASSWORD=replace-with-a-strong-secret \
  pgsty/minio:latest server /data --console-address :9001
Example credentials are for local testing only. Enable TLS, use unique strong credentials, and test recovery before production.

02 / ADMIN CLI

mcli Client

File transfer and administration commands for SILO, MinIO, and general S3-compatible storage. Standalone artifacts use the mcli command name.

CURRENT VERSION 2026-04-17 Release notes & all artifacts ↗
MCLI / NATIVE PACKAGES

Install the package for your Linux distribution

RPMDEBAPKSHA-256

DEPLOYMENT TOPOLOGY

Pick topology after you know the failure domain

SILO can start on one machine, but production planning should be explicit about disks, nodes, redundancy, and recovery expectations.

SNSD01 × 01

Single node · single disk

Personal labs, local development, and disposable non-production validation. No data redundancy.

minio server /data DEV / TEST
SNMD01 × 04+

Single node · multiple disks

A resource-constrained compromise that can tolerate some disk failures, but not node failure.

minio server /data{1...4} CONSTRAINED