Files
buzz/docker-compose.harness.yml
Salman Mohammed f3940ff21e fix(ci): pull pinned MinIO images from Quay (#7599)
## Summary

CI is failing in `main` before tests start because Docker Hub denies
pulls for `minio/minio` and `minio/mc`. Retrying the failed jobs
produced the same errors.

Use MinIO’s Quay images in the development, harness, deployment Compose,
and Helm configurations. Pin each image to its multi-platform digest and
retain the release tags already used by deployment templates. Update the
architecture reference to match.

### Related issue

No duplicate issue or PR found. Addresses the image-pull failures in
[main CI attempt
2](https://github.com/block/buzz/actions/runs/34645306855/attempts/2).

### Testing

- Pulled both pinned images for Linux ARM64 and AMD64.
- Started an isolated Compose stack derived from the updated MinIO
service definitions, once per architecture (AMD64 under local
emulation).
- Verified the existing health check passed and the bucket initializer
exited with code 0.
- Uploaded an object with `mc cp`, read it with `mc cat`, compared its
content, and deleted it with `mc rm` on both architectures.
- Confirmed the initialized bucket was private and removed the temporary
stack and volume.

Generated with Codex

Signed-off-by: Salman Mohammed <smohammed@squareup.com>
2026-09-12 10:33:10 -06:00

78 lines
2.4 KiB
YAML

# =============================================================================
# Isolated test-relay backing stack — GUI read-model overhaul harness (Dawn).
#
# A SEPARATE Compose project (`buzz-harness`) so the shared :3000 relay and the
# default `buzz-*` dev stack are never touched. No fixed container_names (they
# collide across projects) and alternate host ports. Mirrors Eva's evaperf-*
# isolation pattern.
#
# Bring up: docker compose -p buzz-harness -f docker-compose.harness.yml up -d
# Ports: postgres 5471 · redis 6471 · minio 9471/9472
# Relay (run separately by scripts/start-isolated-test-relay.sh):
# main 3030 · health 8088 · metrics 9202
# =============================================================================
services:
postgres:
image: postgres:17-alpine
environment:
POSTGRES_USER: buzz
POSTGRES_PASSWORD: buzz_dev
POSTGRES_DB: buzz
PGDATA: /var/lib/postgresql/data
ports:
- "5471:5432"
volumes:
- harness-postgres-data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U buzz"]
interval: 5s
timeout: 5s
retries: 10
start_period: 10s
redis:
image: redis:7-alpine
ports:
- "6471:6379"
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 5s
timeout: 3s
retries: 10
start_period: 5s
minio:
image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z@sha256:14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e
command: server /data --console-address ":9001"
environment:
MINIO_ROOT_USER: buzz_dev
MINIO_ROOT_PASSWORD: buzz_dev_secret
ports:
- "9471:9000"
- "9472:9001"
volumes:
- harness-minio-data:/data
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
interval: 5s
timeout: 5s
retries: 10
start_period: 10s
minio-init:
image: quay.io/minio/mc:RELEASE.2025-08-13T08-35-41Z@sha256:a7fe349ef4bd8521fb8497f55c6042871b2ae640607cf99d9bede5e9bdf11727
depends_on:
minio:
condition: service_healthy
entrypoint: >
/bin/sh -c "
mc alias set local http://minio:9000 buzz_dev buzz_dev_secret &&
mc mb --ignore-existing local/buzz-media &&
mc anonymous set none local/buzz-media
"
restart: "no"
volumes:
harness-postgres-data:
harness-minio-data: