Use case
The minio/minio image can no longer be pulled: the upstream MinIO repository was archived on 24 April 2026 (the community edition is now source-only), and Docker Hub has since removed the minio/minio and minio/mc repositories altogether - every tag answers 404 and docker pull fails with pull access denied for minio/minio. Every fresh deployment or CI run of a stack that still references these images is broken today.
Following OpenCTI-Platform/opencti#18239, the stack moves to Silo, the community-maintained fork of the MinIO server published by Pigsty (pgsty/silo on Docker Hub, amd64 and arm64). Silo keeps the S3 API, the MINIO_* variables, the server /data --console-address command, the /minio/health/live route, the bundled mc client (so mc ready local healthchecks keep working) and the on-disk format unchanged, so an existing data volume is reused as is.
The latest tag is used on purpose: the MinIO-style dated release tags are not tracked anymore, and the whole Filigran ecosystem is aligned on pgsty/silo:latest (and pgsty/mc:latest for the client).
Current workaround
Pull the frozen images from quay.io/minio/minio (still online for now) or mirror them to a private registry.
Proposed solution
Replace minio/minio:latest by pgsty/silo:latest in docker-compose.yml and docker-compose.dev.yml, keeping the service and container names (minio, openaev-dev-minio), ports, credentials, server /data command and mc ready local healthcheck untouched so that MINIO_ENDPOINT=minio and the XTM One / worker S3_ENDPOINT=minio:9000 settings keep working as they are. Update the .env.sample comment that names MinIO as the object storage of the stack.
Additional information
Use case
The
minio/minioimage can no longer be pulled: the upstream MinIO repository was archived on 24 April 2026 (the community edition is now source-only), and Docker Hub has since removed theminio/minioandminio/mcrepositories altogether - every tag answers 404 anddocker pullfails withpull access denied for minio/minio. Every fresh deployment or CI run of a stack that still references these images is broken today.Following OpenCTI-Platform/opencti#18239, the stack moves to Silo, the community-maintained fork of the MinIO server published by Pigsty (
pgsty/siloon Docker Hub, amd64 and arm64). Silo keeps the S3 API, theMINIO_*variables, theserver /data --console-addresscommand, the/minio/health/liveroute, the bundledmcclient (somc ready localhealthchecks keep working) and the on-disk format unchanged, so an existing data volume is reused as is.The
latesttag is used on purpose: the MinIO-style dated release tags are not tracked anymore, and the whole Filigran ecosystem is aligned onpgsty/silo:latest(andpgsty/mc:latestfor the client).Current workaround
Pull the frozen images from
quay.io/minio/minio(still online for now) or mirror them to a private registry.Proposed solution
Replace
minio/minio:latestbypgsty/silo:latestindocker-compose.ymlanddocker-compose.dev.yml, keeping the service and container names (minio,openaev-dev-minio), ports, credentials,server /datacommand andmc ready localhealthcheck untouched so thatMINIO_ENDPOINT=minioand the XTM One / workerS3_ENDPOINT=minio:9000settings keep working as they are. Update the.env.samplecomment that names MinIO as the object storage of the stack.Additional information