RHEL · Rocky · Alma · Fedora
DOWNLOAD MATRIX
Download & Install SILO
Choose the server or admin client first, then use the install path that matches your operating system, architecture, and deployment model.
DATA SERVICE
SILO Server
Server binaries, container images, Linux packages, source, and Pigsty Ansible automation.
ADMIN CLI
mcli Client
A compatible command-line client for buckets, objects, identity, cluster administration, and daily operations.
01 / DATA SERVICE
SILO Server
From local validation to a multi-node production cluster, choose the delivery path that matches your control boundary.
Run a persistent instance in minutes
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.
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 :9001Run SILO with the Tenant Helm Chart
The current MinIO Operator Tenant Chart supports overriding the tenant image repository, tag, or digest. Download the official values.yaml, point tenant.image at pgsty/minio, then configure pools and PVCs for your failure domains.
tenant:
image:
repository: pgsty/minio
tag: latest
pullPolicy: IfNotPresentlatest tag is illustrative. In production, pin a tested tag or digest and review pools, StorageClass, anti-affinity, TLS, and tenant credentials before installation.Install with native system packages
Every release includes x86_64 and ARM64 packages. Download the current build directly, or use GitHub Releases for older versions.
Debian · Ubuntu
Alpine Linux
Download native, installer-free binaries
Useful for CI, offline delivery, and hosts where you manage the systemd unit yourself. Every archive comes from the same GitHub release.
Linux
GNU / musl environmentsmacOS
Intel / Apple SiliconWindows
PowerShell / Windows Servercurl -fLO https://github.com/pgsty/minio/releases/download/RELEASE.2026-06-18T00-00-00Z/minio_20260618000000.0.0_linux_amd64.tar.gz
tar -xzf minio_20260618000000.0.0_linux_amd64.tar.gz
sudo install -m 0755 minio /usr/local/bin/minio
minio --versionDeliver an operable SILO cluster with Ansible
Pigsty's MINIO module uses minio.yml to install packages, configure directories and certificates, launch systemd services, register monitoring, and provision aliases, buckets, and users. It fits deployments that need declarative configuration, TLS, and multi-node multi-disk topology.
Prepare the control node
curl -fsSL https://repo.pigsty.io/get | bash
cd ~/pigsty
./bootstrap
./configure -gDefine the MinIO inventory
minio:
hosts:
10.10.10.10: { minio_seq: 1 }
vars:
minio_cluster: minioRun the install playbook
./minio.yml -l minio
mcli ls sss/Build from the maintained branch
Use this path for auditing, development, or custom build flags. The result is a native minio executable for the current platform.
git clone https://github.com/pgsty/minio.git
cd minio
make build
./minio --version02 / ADMIN CLI
mcli Client
File transfer and administration commands for SILO, MinIO, and general S3-compatible storage. Standalone artifacts use the mcli command name.
Install the package for your Linux distribution
RHEL · Rocky · Alma · Fedora
Debian · Ubuntu
Alpine Linux
Download the cross-platform client directly
Linux
server & workstationmacOS
Intel / Apple SiliconWindows
desktop / servermcli alias set local http://127.0.0.1:9000 ACCESS_KEY SECRET_KEY
Run mcli without installing it on the host
The container retains the familiar mc entrypoint, while standalone archives and Linux packages use mcli.
docker run --rm pgsty/mc:latest --version
docker run --rm pgsty/mc:latest ls playBuild the maintained client
The source keeps the github.com/minio/mc module path and mc build output for compatibility; release archives and packages use mcli.
git clone https://github.com/pgsty/mc.git
cd mc
make build
./mc --versionDEPLOYMENT 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.
Single node · single disk
Personal labs, local development, and disposable non-production validation. No data redundancy.
minio server /data
DEV / TESTSingle node · multiple disks
A resource-constrained compromise that can tolerate some disk failures, but not node failure.
minio server /data{1...4}
CONSTRAINEDMultiple nodes · multiple disks
The standard production topology, with erasure-code redundancy across disk and node failure domains. Recommended with Pigsty Ansible.
https://minio-{1...4}.pigsty/data{1...4}
PRODUCTIONSUPPORT SURFACE
Need a production deployment path?
Move from local validation to production with the full documentation, release notes, and community support for upgrade and recovery planning.
Read the docs
Configuration, deployment, S3 clients, security, and operations guidance.
Browse documentation ↗Report an issue
Share compatibility feedback, installation friction, or reproducible operational issues.
GitHub Issues ↗Pigsty Ansible
Deliver TLS, monitoring, service discovery, and multi-node topology from declarative inventory.
Open deployment module ↗