Skip to content

Pull MinIO from a registry that still serves it #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dimitri-yatsenko merged 1 commit into from
Oct 4, 2026
Merged

Pull MinIO from a registry that still serves it #294

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docker-compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,18 @@ services:
retries: 10

minio:
image: minio/minio:latest
# MinIO withdrew its public images: `minio/minio` on Docker Hub is gone
# entirely, any tag, and `quay.io/minio/minio` now requires authentication.
# Chainguard publishes a maintained build that needs no credentials and is
# drop-in here -- it ships `mc`, so the healthcheck below is unchanged.
# Matches what datajoint-python's test fixture uses.
#
# It runs as `nonroot`, and a `minio_data` volume left behind by the old
# root-owned image is not writable by it: MinIO exits with "Unable to write
# to the backend". A fresh volume inherits the image's world-writable /data
# and is fine, so `docker compose down -v` once clears it. CI runners start
# clean and never see this.
image: ${MINIO_IMAGE:-cgr.dev/chainguard/minio:latest}
environment:
MINIO_ROOT_USER: datajoint
MINIO_ROOT_PASSWORD: datajoint
Expand Down