fix(docker): pull minio from quay.io

[Bilal-dev2134]

Fixes #231.

MinIO removed their entire namespace from Docker Hub, so minio/minio:RELEASE.2024-11-07T00-52-20Z can no longer be pulled anonymously. Since Compose pulls all image-based services up front, the whole stack fails to start, not just MinIO:

Image minio/minio:RELEASE.2024-11-07T00-52-20Z  Error pull access denied for minio/minio,
repository does not exist or may require 'docker login'

Verified this is the namespace being gone rather than a rate limit — minio/minio, minio/mc and minio/console all return 404 from hub.docker.com and 401 from the registry, while bitnami/minio and library/nginx return 200 from the same unauthenticated script.

Change

One line. MinIO still publishes to quay.io, their own registry, and the exact same tag is there (quay.io/v2/minio/minio/manifests/RELEASE.2024-11-07T00-52-20Z -> 200, multi-arch manifest list, 6 arch children):

   minio:
-    image: minio/minio:RELEASE.2024-11-07T00-52-20Z
+    image: quay.io/minio/minio:RELEASE.2024-11-07T00-52-20Z

Identical version — no upgrade, no config or behaviour change.

Testing

Running this in production since the outage. Full stack comes up clean (all 10 containers, db healthy), and an end-to-end crawl returns correctly extracted markdown stored in and served from MinIO.

[qodo-code-review]

PR Summary by Qodo

Pull MinIO image from Quay.io instead of Docker Hub

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Restores Compose startup by pulling MinIO from its available Quay.io namespace.
• Preserves the existing MinIO release tag and runtime behavior.

High-Level Assessment

Using MinIO's official Quay.io namespace with the identical release tag is the lowest-risk solution. Switching versions, using an unofficial mirror, or rebuilding the image would introduce unnecessary compatibility or supply-chain risk.

Files changed (1) +1 / -1

Bug fix (1) +1 / -1

docker-compose.ymlSource the MinIO image from Quay.io +1/-1

Source the MinIO image from Quay.io

• Replaces the unavailable Docker Hub image reference with MinIO's Quay.io registry path. The pinned release tag remains unchanged, preserving existing configuration and behavior.

docker/docker-compose.yml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Local development still pulls deleted image 🐞 Bug ≡ Correctness

Description

The production Compose file switches MinIO to Quay, but docker-compose.local.yml still requests
minio/minio:RELEASE.2024-11-07T00-52-20Z from Docker Hub. Developers following the documented
local setup therefore continue to receive the same pull failure and cannot start their development
stack.

Code

docker/docker-compose.yml[171]

+    image: quay.io/minio/minio:RELEASE.2024-11-07T00-52-20Z

Evidence

The local development setup explicitly starts docker-compose.local.yml, whose MinIO service still
uses the deleted Docker Hub namespace. The self-hosted services documentation also records the old
image reference, so the registry migration is incomplete across supported configurations.

docker/docker-compose.local.yml[27-32]
CONTRIBUTING.md[36-36]
DEV_SETUP.md[39-39]
docs/docs/self-hosted/services.md[86-95]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The production Compose file uses `quay.io/minio/minio`, but the supported local development Compose file still uses the removed Docker Hub namespace, so the documented local setup remains unable to pull MinIO.

## Fix Focus Areas
- docker/docker-compose.local.yml[27-28]
- docs/docs/self-hosted/services.md[86-87]

## Recommended Fix
Change the MinIO image in `docker/docker-compose.local.yml` to `quay.io/minio/minio:RELEASE.2024-11-07T00-52-20Z` and update the MinIO image reference in the self-hosted services documentation so all supported setup paths describe the working registry.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

Review mode: 🚀 Fast: This is a single, localized Docker image registry change with a contained operational impact and no security, schema, API, or logic complexity.

Tip of the day

💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Local development still pulls deleted image 🐞 Bug ≡ Correctness

The production Compose file switches MinIO to Quay, but docker-compose.local.yml still requests
minio/minio:RELEASE.2024-11-07T00-52-20Z from Docker Hub. Developers following the documented
local setup therefore continue to receive the same pull failure and cannot start their development
stack.

Agent Prompt

## Issue description
The production Compose file uses `quay.io/minio/minio`, but the supported local development Compose file still uses the removed Docker Hub namespace, so the documented local setup remains unable to pull MinIO.

## Fix Focus Areas
- docker/docker-compose.local.yml[27-28]
- docs/docs/self-hosted/services.md[86-87]

## Recommended Fix
Change the MinIO image in `docker/docker-compose.local.yml` to `quay.io/minio/minio:RELEASE.2024-11-07T00-52-20Z` and update the MinIO image reference in the self-hosted services documentation so all supported setup paths describe the working registry.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools