Pin MinIO to the pgsty community fork - #91
Merged
Merged
Conversation
Upstream MinIO images are no longer pullable: quay.io/minio/minio and Docker Hub minio/minio return 401, which broke the Docker Compose smoke and backup/restore jobs. Pin the AGPL-3.0 pgsty/minio fork by multi-arch digest in Compose, Dokploy, Railway, and the backup/restore smoke. It is the same server and bundled mc with identical env vars, health endpoint, and on-disk format, so existing minio-data volumes start unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
quay.io/minio/minio@sha256:14cea49…can no longer be pulled (quay returns 401, even for the public repository API). Docker Hubminio/minioandminio/mcalso return 401, and upstreamminio/miniois archived. As a result, Docker Compose self-host smoke and Docker Compose backup and restore fail withminio Error unauthorized(Validate run 36269435723).Change
docker.io/pgsty/minio@sha256:b6bfe7239bfc83fb90d31612d9704d86039dd714f7904b3f1ad68f211e602372(RELEASE.2026-08-04T00-00-00Z, multi-arch amd64 and arm64) incompose.yaml, the Dokploy blueprint, the Railway contract, andscripts/self-host-backup-restore-smoke.sh(this pin also providesmc).docs/self-hosting.mdanddeploy/railway/README.mdto say where the image comes from and how existing installs upgrade.Why this fork
miniobinary,MINIO_ROOT_*env vars,/minio/health/live,curlfor the healthcheck, bundledmc, and entrypoint. The on-disk format is also the same, so existingminio-datavolumes need no migration.GK…key IDs breakMINIO_ROOT_USER=blogfactory) and a data migration for existing installs.Verification
bash scripts/self-host-smoke.shpassed locally.bash scripts/self-host-backup-restore-smoke.shpassed locally.git diff --checkis clean.🤖 Generated with Claude Code