chore(compose): replace the MinIO image by pgsty/silo in the compose stacks (#162)

[Samuel Hassine (SamuelHassine)]

Proposed changes

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).

• docker-compose.yml: minio/minio:latest becomes pgsty/silo:latest on the minio service;
• docker-compose.dev.yml: same change on openaev-dev-minio;
• .env.sample: the comment that named MinIO as the object storage of the stack now names Silo.

Service and container names (minio, openaev-dev-minio), ports, credentials, server /data command and mc ready local healthcheck are untouched, so MINIO_ENDPOINT=minio, the XTM One S3_ENDPOINT=minio:9000 settings and existing .env files keep working as they are. An existing s3data volume is reused as is (same on-disk format).

Related issues

• Closes chore(compose): replace the MinIO image by pgsty/silo in the compose stacks #162

How to test this PR

cp .env.sample .env
docker compose up -d minio
docker compose ps minio            # healthy
curl -f http://localhost:9000/minio/health/live

Then start the full stack and upload a document: it lands in the bucket exactly as before.

Verified locally with Docker 29.6 on pgsty/silo:RELEASE.2026-09-03T13-18-01Z (the current latest) with the exact compose settings of the stack: the container reaches healthy through mc ready local, /minio/health/live and the console on 9001 answer 200, and a bucket create / upload / read round trip works with pgsty/mc. The image ships /usr/bin/mc, /usr/bin/mcli and /usr/bin/curl, so both healthcheck styles used across the Filigran stacks are supported.

Checklist

• The PR title follows the Conventional Commits convention type(scope?): description (#issue)
• I signed my commits
• This PR is linked to an issue
• I consider the submitted work as finished
• I tested the code for its functionality
• I added/updated the relevant documentation
• Where necessary, I refactored code to improve the overall quality

Further comments

Same change as OpenCTI-Platform/docker#607; the whole Filigran ecosystem is being moved to pgsty/silo:latest in one pass.

[Copilot]

Pull request overview

Replaces unavailable MinIO images with pgsty/silo:latest while preserving existing storage configuration.

Changes:

• Updated production and development Compose images.
• Updated .env.sample to reference Silo.
• Preserved service configuration, healthchecks, and volumes.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
docker-compose.yml	Uses Silo for object storage.
docker-compose.dev.yml	Uses Silo in the development stack.
.env.sample	Identifies Silo as the S3 storage provider.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.