# minio-build MinIO server and `mc` client images, built from upstream's AGPLv3 source at release tags and published to `gitea.malogica.net/mirror`. **Why:** upstream no longer publishes pullable images. `minio/minio` on Docker Hub returns 404, `quay.io/minio/minio` requires authentication, and the `dl.min.io` binary channel returns 410. Any fresh pull fails, which broke CI in MIND and OFFICE in September 2026. This is a stopgap until we pick a replacement S3-compatible store. ## Images The `mirror` org is public, so pulls need no login. | Image | Bundles `mc` | Used by | |---|---|---| | `gitea.malogica.net/mirror/minio:RELEASE.2024-01-16T16-07-38Z` | `RELEASE.2024-01-13T08-44-48Z` | OFFICE | | `gitea.malogica.net/mirror/minio:RELEASE.2025-04-22T22-12-26Z` | `RELEASE.2025-04-16T18-13-26Z` | EVCCFLEET | | `gitea.malogica.net/mirror/minio:RELEASE.2025-10-15T17-29-55Z` | `RELEASE.2025-08-13T08-35-41Z` | new work (last source release) | | `gitea.malogica.net/mirror/mc:` | | compose init jobs | Each is multi-arch (`linux/amd64`, `linux/arm64`). They are drop-ins for `quay.io/minio/minio`: - `server /data` runs `minio server /data`. - `mc`, `curl` and `sh` are included (healthchecks and `--entrypoint=/bin/sh` init scripts work). - `MINIO_USERNAME`/`MINIO_GROUPNAME` drop privileges as upstream does. - `minio --version` reports the real release and upstream commit. Testcontainers: `new MinIOContainer(DockerImageName.parse("gitea.malogica.net/mirror/minio:RELEASE.2025-10-15T17-29-55Z").asCompatibleSubstituteFor("minio/minio"))`. ## Build ```sh ./build.sh local.test/mirror # host platform only, loaded locally for testing ./build.sh gitea.malogica.net/mirror --push # amd64 + arm64, pushed (needs a write:package login) ``` To add a release, append a line to the list in `build.sh`: minio tag, `mc` tag, Go toolchain.