fix(deploy): default MinIO images to maintained pgsty/silo + pgsty/mc, make repositories configurable

[Shaan-Shoukath]

Why

Every fresh self-host install failed at docker compose pull with pull access denied for minio/mc. MinIO has removed its community images from Docker Hub (minio/minio and minio/mc both return 404), and quay.io/minio/* refuses anonymous pulls. Existing installs keep working only while the image stays in their local Docker cache.

What

• Compose files. docker-compose.prod.yml and docker-compose.yml now use ${MINIO_IMAGE:-pgsty/silo}:${MINIO_IMAGE_TAG:-RELEASE.2026-09-16T00-00-00Z} and ${MC_IMAGE:-pgsty/mc}:${MC_IMAGE_TAG:-RELEASE.2026-09-16T00-00-00Z}. The *_IMAGE variables take a repository name only. command, the healthcheck and the bucket-setup script are unchanged, because Silo's entrypoint passes server … to the silo binary.
• Rejected alternatives. Chainguard and the -distroless variants have no sh/curl, which the healthcheck and createbuckets need. bitnamilegacy is frozen.
• New test. backend/tests/test_object_storage_images.py checks the defaults are overridable, pinned, outside the retired namespaces, and the same in dev and prod.
• Docs. self-hosting.md gains an "Object storage images" section covering existing-host adoption and rollback. The minio_data backup command is rewritten because Silo has no tar, and restore now checks the archive before clearing the volume. The topology-fingerprint wording is corrected. deploy-ec2.md, INVARIANTS.md and PROJECT-HISTORY.md are updated too.

Verified locally

• A minio_data volume written by MinIO RELEASE.2025-09-07T16-13-09Z (the previous pin) was served by Silo RELEASE.2026-09-16T00-00-00Z.
  • Object versions, delete markers, versioning state and bucket policies were all intact.
  • Bucket setup re-ran cleanly.
  • Anonymous GET returned 200 on the public bucket and 403 on evidence.
  • CORS preflight passed.
  • Presigned POST returned 204, with 403 for a wrong MIME type and 400 for an oversize upload. Presigned PUT returned 200.
• The documented backup/restore round trip restores exactly. A missing or corrupt archive leaves existing data untouched.
• docker compose config was checked with variables unset, empty, overridden (including a registry with a port), and with a stale tag pin.
• The new test plus test_env_surface_drift and test_bundled_cookie_posture: 35 passed.

Existing hosts

update.sh does not ship compose files. To adopt this on an existing host: back up minio_data, install the new docker-compose.prod.yml, then run bash scripts/init-host-orchestration.sh and pull/up -d.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for kanakkupusthakam canceled.

Name	Link
🔨 Latest commit	09f55a6
🔍 Latest deploy log	https://app.netlify.com/projects/kanakkupusthakam/deploys/6ace46b3d2ddba1da15f18b4

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5862a618-ad05-4ab3-8dc4-1e34908fe72c

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}