silo

Silo Docker Image

Silo是PGSTY维护的MinIO分支,提供兼容S3/MinIO的对象存储服务,支持现有MinIO部署的维护构建,可作为PostgreSQL备份存储库等场景使用。

5 次收藏下载次数: 0状态:社区镜像维护者:pgsty仓库类型:镜像最近更新:
下载命令
点击查看

S3-compatible object storage — a MinIO fork maintained by PIGSTY

Website · Documentation · Download · Release Notes · Compatibility · Security · 中文

https://github.com/pgsty/silo/releases https://hub.docker.com/r/pgsty/silo

[!IMPORTANT] Silo is an independent, community-maintained fork of the open-source MinIO server, published by Pigsty from pgsty/silo. It is not affiliated with, endorsed by, or sponsored by MinIO, Inc. “MinIO” is used only to identify the upstream project and compatibility lineage.

[!NOTE] This repository was renamed from pgsty/minio to pgsty/silo,

Overview

Silo maintains one downstream release line derived from the open-source MinIO server. It provides maintained builds and release artifacts for existing MinIO-compatible deployments after upstream community distribution ended. Pigsty uses Silo for object storage, including as an optional PostgreSQL backup repository.

The fork follows one rule: the product and its delivery surfaces are renamed; the protocol and your data are not. The silo executable, packages, service, and container image carry the new name, while the S3 API, MINIO_* variables, minio_* metrics, x-minio-* headers, reserved routes, and the on-disk format stay unchanged. The differences are recorded in the compatibility notes.

The official project portal is silo.pgsty.com. It brings documentation, downloads, release and security notes, and project background together.

Find the Right Resource

Looking forCanonical location
Project overview and navigationSilo Website
Installation methods and downloadsDownload & Install
Operations, administration, development, and referenceDocumentation
Release notes for this serverSilo release notes
Differences from upstream MinIOSilo vs. MinIO compatibility notes
Project news and security advisoriesBlog · release and security notes
Versioned binaries, checksums, and source archiveshttps://github.com/pgsty/silo/releases
Bug reports and feature discussionshttps://github.com/pgsty/silo/issues
Vulnerability reportinghttps://github.com/pgsty/silo/blob/main/SECURITY.md and https://github.com/pgsty/silo/blob/main/VULNERABILITY_REPORT.md
License, attribution, and trademark informationhttps://github.com/pgsty/silo/blob/main/LICENSE · https://github.com/pgsty/silo/blob/main/NOTICE · https://github.com/pgsty/silo/blob/main/CREDITS · portal license, attribution, and trademark pages

Related Projects

RepositoryDescription
https://github.com/pgsty/siloThis repository — the Silo object storage server, an S3-compatible MinIO fork
https://github.com/pgsty/mcThe Silo command-line client, shipped as mcli with the mc command name
https://github.com/pgsty/silo-consoleAdmin web console, embedded in the server build
https://github.com/pgsty/silo-pkgShared Go packages maintained for the Silo forks
https://github.com/pgsty/pigstyPigsty — the PostgreSQL distribution that ships Silo as its object storage

Maintenance Policy

The active release line covers:

  • build and dependency maintenance;
  • applicable security fixes and advisories;
  • focused fixes for reproducible defects;
  • versioned binaries, packages, checksums, and multi-architecture images;
  • the web console, client, documentation, and Pigsty integration.

Changes are kept narrow and tested where practical. Maintenance is best effort; no response, remediation, or release schedule is guaranteed.

Out of scope

  • a separate product roadmap, new storage engine, or speculative S3 features;
  • broad rewrites or changes that materially expand the downstream delta;
  • historical releases or multiple support branches;
  • commercial support, SLAs, 24×7 coverage, or SUBNET access;
  • deployment design, access control, monitoring, backup, or recovery.

Governance

The server, client, console, and shared packages are maintained under one release process: DCO-signed commits, reviewed pull requests, and versioned RELEASE.YYYY-MM-DDTHH-MM-SSZ tags whose artifacts ship with checksums, SPDX SBOMs, Sigstore-signed manifests, and GitHub build attestations. Each release is announced with a release note on the portal; security handling follows https://github.com/pgsty/silo/blob/main/SECURITY.md and the https://github.com/pgsty/silo/blob/main/docs/security/advisories.md. Upstream copyright, license, and third-party notices are preserved in https://github.com/pgsty/silo/blob/main/LICENSE, https://github.com/pgsty/silo/blob/main/NOTICE, and https://github.com/pgsty/silo/blob/main/CREDITS.

Compatibility

Silo aims to preserve:

  • the github.com/minio/minio module path and github.com/minio/* import paths;
  • MinIO-compatible S3 APIs, wire behavior, MINIO_* environment variables, metrics, protocol headers, reserved routes, and storage metadata;
  • RELEASE.YYYY-MM-DDTHH-MM-SSZ tags and legacy minio … container argv translation.

Silo-owned delivery surfaces use the silo executable, package, service, Helm chart, and pgsty/silo container image. Native artifacts intentionally do not install a minio binary alias.

Compatibility is the default constraint. Silo preserves existing wire, client, configuration, and operational behavior whenever doing so remains safe. Compatibility is broken only when necessary to close a major security issue, and the release notes must identify the affected behavior and migration path. Treat each release as a downstream upgrade: pin versions, review the release notes, compatibility notes, and https://github.com/pgsty/silo/blob/main/docs/security/advisories.md, keep a rollback path, and test before production use.

Downloads and Release Artifacts

Use Download & Install to choose an installation method. GitHub Releases remains the source for versioned server binaries, checksums, and source archives.

ArtifactLocation
Sourcehttps://github.com/pgsty/silo
Container imagehttps://hub.docker.com/r/pgsty/silo, multi-arch for linux/amd64 and linux/arm64
Server binaries and checksumshttps://github.com/pgsty/silo/releases for Linux, macOS, and Windows on amd64 and arm64
Linux packagesRPM, DEB, and APK artifacts, also distributed through the Pigsty repository
Clienthttps://github.com/pgsty/mc, bundled in the container as mcli with an mc compatibility alias
Consolehttps://github.com/pgsty/silo-console, embedded through the compatibility import path github.com/minio/console
Shared libraryhttps://github.com/pgsty/silo-pkg v3.11.0, consumed through a replace directive while preserving the github.com/minio/pkg/v3 import path

Each new release publishes per-archive and per-package SPDX JSON SBOMs. The archive and package checksum manifests have detached keyless Sigstore bundles, while GitHub artifact attestations record signed provenance for every downloadable artifact and the multi-architecture container image.

After downloading an archive and its release files, verify integrity, the published SBOM, the signed manifest, and build provenance independently:

# Integrity: choose the line for the artifact you downloaded.
grep -F '  silo_<version>_linux_amd64.tar.gz' \
  silo_<version>_checksums.txt | sha256sum --check

# The archive SBOM is a separate checksummed release artifact.
grep -F '  silo_<version>_linux_amd64.tar.gz.sbom.json' \
  silo_<version>_checksums.txt | sha256sum --check

# Signature over the archive/SBOM checksum manifest.
cosign verify-blob \
  --bundle silo_<version>_checksums.txt.sigstore.json \
  --certificate-identity-regexp \
    '^https://github.com/pgsty/(minio|silo)/\.github/workflows/release\.yml@refs/(tags/RELEASE\..+|heads/(master|main))

For packages, use `silo_<version>_packages_checksums.txt` and its adjacent Sigstore bundle with the same identity and issuer constraints. Inspect the verified SPDX JSON SBOM with your preferred SPDX tooling. Verify the multi-architecture container provenance by digest:

gh attestation verify
oci://index.docker.io/pgsty/silo@sha256:
--repo pgsty/silo


The platform SBOM attestations are attached to the `amd64` and `arm64` image digests rather than the multi-architecture manifest. Verify each one explicitly:

gh attestation verify
oci://index.docker.io/pgsty/silo@sha256:
--repo pgsty/silo
--predicate-type https://spdx.dev/Document/v2.3


Verification by digest avoids trusting a mutable image tag.

### Native package migration

The `silo` RPM, DEB, and APK do not declare `Provides`, `Obsoletes`, `Replaces`, or package-level `Conflicts` against `minio`. They can therefore be installed beside an existing MinIO package without silently replacing it. The two systemd units conflict at runtime, so switch them explicitly rather than starting both.

Before switching, record the old unit's enabled/active state and `User`/`Group`, and back up `/etc/default/minio`. Silo reads that legacy defaults file first and then `/etc/default/silo`; administrator-set values in the latter take precedence. If the existing data must continue to run under its original UID/GID, create `/etc/systemd/system/silo.service.d/10-legacy-user.conf`:

[Service] User= Group=


Run `systemctl daemon-reload`, then disable and stop `minio.service` before enabling and starting `silo.service`. Verify health, S3, Admin API, metrics, and logs before masking or uninstalling the old service. Do not recursively change data ownership as part of the package migration; keep the old package and unit available during the rollback window.

## Quick Start

For local evaluation:

mkdir -p data

export MINIO_ROOT_USER=minioadmin export MINIO_ROOT_PASSWORD=change-me-long-password

docker run -d --name silo
-p 9000:9000
-p 9001:9001
-e MINIO_ROOT_USER
-e MINIO_ROOT_PASSWORD
-v "$PWD/data:/data"
docker.io/pgsty/silo:latest server /data --console-address ":9001"


Open the console at http://localhost:9001/; the S3 API listens on http://localhost:9000/.

The image includes the compatible client as `mcli`:

docker exec silo mcli alias set local http://127.0.0.1:9000
"$MINIO_ROOT_USER" "$MINIO_ROOT_PASSWORD" docker exec silo mcli mb local/demo docker exec silo mcli ls local


Warning

For production, pin a release, use unique credentials and TLS, monitor the service, keep independent backups, and test recovery.

Build the server from source:

go build -o silo . ./silo --version


For other installation paths—including native packages, binaries, Podman, Kubernetes, source, and Pigsty Ansible—use Download & Install. For production deployment and administration, start with the Silo documentation. Pigsty users can also use the Pigsty MinIO module.

## Security

Security fixes target the active development branch and are recorded in the https://github.com/pgsty/silo/blob/main/docs/security/advisories.md and the portal's security notes. Report vulnerabilities privately as described in https://github.com/pgsty/silo/blob/main/SECURITY.md and https://github.com/pgsty/silo/blob/main/VULNERABILITY_REPORT.md. Report issues that also affect upstream MinIO there as well.

## Contributing

Useful contributions include security and dependency updates, reproducible bug fixes, tests, release automation, packaging, and documentation.

Issues and pull requests should include the affected version, reproduction steps, impact, expected behavior, tests, and compatibility notes. Discuss large changes in an issue first.

There is no CLA: contributions are accepted inbound=outbound under the project license (AGPL-3.0-or-later) and contributors keep their copyright. Every commit must be signed off (`git commit -s`) per the Developer Certificate of Origin; see https://github.com/pgsty/silo/blob/main/CONTRIBUTING.md.

## Background

This project was created in response to changes in the upstream community distribution and maintenance model. The maintainer’s analysis, alternatives ***ed, and early maintenance record are documented below:

| Essay                                                        | Subject                                                |
| ------------------------------------------------------------ | ------------------------------------------------------ |
| MinIO Is Dead | Changes to the upstream project and distribution model |
| MinIO Is Dead, Who Takes Over? | Alternatives ***ed                                |
| MinIO Is Dead, Long Live MinIO | Establishing the fork and its release pipeline         |
| Two months into maintaining a MinIO fork | Initial security and maintenance work                  |

## License and Trademark

The server source is distributed under the https://github.com/pgsty/silo/blob/main/LICENSE. This fork derives from https://github.com/minio/minio: https://github.com/pgsty/silo/blob/main/NOTICE retains the upstream product notice, https://github.com/pgsty/silo/blob/main/CREDITS records licenses and notices for included third-party components, and the Git history records downstream modifications.

MinIO is a trademark of MinIO, Inc. The name is used here only to identify the upstream project and compatibility lineage. Pigsty, Silo, and `pgsty/silo` are independent community efforts and are not affiliated with, endorsed by, or sponsored by MinIO, Inc.

The portal separately publishes the project license summary, documentation attribution, and trademark notice. \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  silo_<version>_checksums.txt

# Signed build provenance (online verification against this repository).
gh attestation verify silo_<version>_linux_amd64.tar.gz \
  --repo pgsty/silo

For packages, use CODE_TOKEN_50 and its adjacent Sigstore bundle with the same identity and issuer constraints. Inspect the verified SPDX JSON SBOM with your preferred SPDX tooling. Verify the multi-architecture container provenance by digest:

CODE_TOKEN_1

The platform SBOM attestations are attached to the CODE_TOKEN_51 and CODE_TOKEN_52 image digests rather than the multi-architecture manifest. Verify each one explicitly:

CODE_TOKEN_2

Verification by digest avoids trusting a mutable image tag.

Native package migration

The CODE_TOKEN_53 RPM, DEB, and APK do not declare CODE_TOKEN_54, CODE_TOKEN_55, CODE_TOKEN_56, or package-level CODE_TOKEN_57 against CODE_TOKEN_58. They can therefore be installed beside an existing MinIO package without silently replacing it. The two systemd units conflict at runtime, so switch them explicitly rather than starting both.

Before switching, record the old unit's enabled/active state and CODE_TOKEN_59/CODE_TOKEN_60, and back up CODE_TOKEN_61. Silo reads that legacy defaults file first and then CODE_TOKEN_62; administrator-set values in the latter take precedence. If the existing data must continue to run under its original UID/GID, create CODE_TOKEN_63:

CODE_TOKEN_3

Run CODE_TOKEN_64, then disable and stop CODE_TOKEN_65 before enabling and starting CODE_TOKEN_66. Verify health, S3, Admin API, metrics, and logs before masking or uninstalling the old service. Do not recursively change data ownership as part of the package migration; keep the old package and unit available during the rollback window.

Quick Start

For local evaluation:

CODE_TOKEN_4

Open the console at http://localhost:9001/; the S3 API listens on http://localhost:9000/.

The image includes the compatible client as CODE_TOKEN_67:

CODE_TOKEN_5

Warning

For production, pin a release, use unique credentials and TLS, monitor the service, keep independent backups, and test recovery.

Build the server from source:

CODE_TOKEN_6

For other installation paths—including native packages, binaries, Podman, Kubernetes, source, and Pigsty Ansible—use Download & Install. For production deployment and administration, start with the Silo documentation. Pigsty users can also use the Pigsty MinIO module.

Security

Security fixes target the active development branch and are recorded in the https://github.com/pgsty/silo/blob/main/docs/security/advisories.md and the portal's security notes. Report vulnerabilities privately as described in https://github.com/pgsty/silo/blob/main/SECURITY.md and https://github.com/pgsty/silo/blob/main/VULNERABILITY_REPORT.md. Report issues that also affect upstream MinIO there as well.

Contributing

Useful contributions include security and dependency updates, reproducible bug fixes, tests, release automation, packaging, and documentation.

Issues and pull requests should include the affected version, reproduction steps, impact, expected behavior, tests, and compatibility notes. Discuss large changes in an issue first.

There is no CLA: contributions are accepted inbound=outbound under the project license (AGPL-3.0-or-later) and contributors keep their copyright. Every commit must be signed off (CODE_TOKEN_70) per the Developer Certificate of Origin; see https://github.com/pgsty/silo/blob/main/CONTRIBUTING.md.

Background

This project was created in response to changes in the upstream community distribution and maintenance model. The maintainer’s analysis, alternatives ***ed, and early maintenance record are documented below:

EssaySubject
MinIO Is DeadChanges to the upstream project and distribution model
MinIO Is Dead, Who Takes Over?Alternatives ***ed
MinIO Is Dead, Long Live MinIOEstablishing the fork and its release pipeline
Two months into maintaining a MinIO forkInitial security and maintenance work

License and Trademark

The server source is distributed under the https://github.com/pgsty/silo/blob/main/LICENSE. This fork derives from https://github.com/minio/minio: https://github.com/pgsty/silo/blob/main/NOTICE retains the upstream product notice, https://github.com/pgsty/silo/blob/main/CREDITS records licenses and notices for included third-party components, and the Git history records downstream modifications.

MinIO is a trademark of MinIO, Inc. The name is used here only to identify the upstream project and compatibility lineage. Pigsty, Silo, and CODE_TOKEN_75 are independent community efforts and are not affiliated with, endorsed by, or sponsored by MinIO, Inc.

The portal separately publishes the project license summary, documentation attribution, and trademark notice.

镜像拉取方式

您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

轩辕镜像加速拉取命令点我查看更多 silo 镜像标签

docker pull docker.xuanyuan.run/pgsty/silo:<标签>

DockerHub 原生拉取命令

docker pull pgsty/silo:<标签>
专业版 · 高速稳定拉取镜像
50GB 仅 ¥8/年
高速镜像下载在线技术支持专业版保障服务可用付费会员免广告