Skip to content

fix(deploy): point MinIO at quay.io — the Docker Hub repository is gone - #176

Merged
acamarata merged 1 commit into
mainfrom
fix/minio-image-moved-to-quay
Sep 14, 2026
Merged

acamarata merged 1 commit into
mainfrom
fix/minio-image-moved-to-quay

Conversation

@acamarata

Copy link
Copy Markdown
Collaborator

MinIO removed minio/minio from Docker Hub.

check result
hub.docker.com/v2/repositories/minio/minio/ {"message":"object not found"}
manifest by tag, anonymous / authenticated 401 / 401
manifest by the pinned digest 401
quay.io/minio/minio, same digest 200

Authenticating does not help — tested with valid Docker Hub credentials. The repository is gone, not gated.

This one is production

backend/deploy/docker-compose.production.override.yml is the live stack. The running container keeps going from its local image, but any redeploy, restart with pull, or new box cannot fetch it.

The digest pin is preserved exactly

The comment above the line pins by digest on purpose ("latest on a stateful store means a restart can jump versions silently"). That rationale is untouched — quay.io serves the same manifest bytes:

HEAD quay.io/v2/minio/minio/manifests/RELEASE.2025-09-07T16-13-09Z
docker-content-digest: sha256:14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e

Byte-identical to the existing pin. Only the registry prefix changes; the image is the same image.

Scope

The production override, .github/wiki/Backend-Architecture.md, backend/README.md.

Related

Upstream generator fix: nself-org/cli#424, which also adds a daily gate resolving every default image with docker manifest inspect — the check whose absence let this pin rot. Same fix in nchat#178 and admin#108.

MinIO removed minio/minio from Docker Hub. The Hub API answers
{"message":"object not found"} for the repository and every reference,
digest pins included, returns 401 to anonymous and authenticated requests
alike. This is production's storage service: the container keeps running
from its local image, but any redeploy, restart with pull, or new box
cannot fetch it.

The pinned digest is unchanged and still exact. quay.io serves the same
manifest bytes: a HEAD for RELEASE.2025-09-07T16-13-09Z there returns
docker-content-digest sha256:14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e,
byte-identical to the pin. Only the registry prefix changes, so the
digest-pinning rationale in the comment above it still holds exactly.

Upstream generator fix: nself-org/cli#424, which also adds a daily gate
resolving every default image so a pin cannot rot unnoticed again.
@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
ntask-web Ignored Ignored Preview Sep 14, 2026 11:32am UTC

Request Review

@acamarata
acamarata merged commit cbd8961 into main Sep 14, 2026
16 checks passed
@acamarata
acamarata deleted the fix/minio-image-moved-to-quay branch September 14, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant