[Olivier SOTIN (T0t1n)]

Proposed changes

• octi-lab/docker-compose.yml: the minio service runs rustfs/rustfs:1.0.4 instead of pgsty/silo:latest, with the service settings of chore(compose): run RustFS as the object storage of the stacks (#620) docker#621 (open): credentials passed as RUSTFS_ACCESS_KEY / RUSTFS_SECRET_KEY from the same MINIO_ROOT_* variables, logs to stdout, no update check at start, healthcheck curl -f http://localhost:9000/health/ready with start_period: 60s. Service name and port 9000 are unchanged, so the OpenCTI (MINIO__*) and XTM One (S3_*) settings of the lab stay as they are.
• New rustfsdata volume instead of s3data: RustFS runs as uid 10001 and does not start on a volume written by Silo (root, Permission denied). This differs from docker#621, which keeps s3data and points to a migration guide: the lab data is disposable, so a fresh volume lets the stack start on a machine that ran the lab before, and a reset replaces the migration.
• octi-lab/README.md: new "Upgrading a lab that ran Silo" section. A lab with a former xtm_s3data volume must be reset (docker compose down -v, then up -d): otherwise the storage is empty while OpenCTI and XTM One keep their data. The former volume is named exactly, with a warning: the OpenCTI-Platform/docker stack uses the same default project name (xtm) and keeps its storage in xtm_s3data.
• octi-lab/.env.sample: the bucket comment names RustFS.

Related issues

• Closes chore(octi-lab): replace pgsty/silo by RustFS in the lab stack #7
• Same change across the ecosystem: feat(storage): support RustFS as an Apache-2.0, S3-compatible alternative to MinIO opencti#16749, feat(storage): run RustFS in the dev and CI stacks and rename the minio configuration section to s3 (#16749) opencti#19371, chore(compose): run RustFS as the object storage of the stacks (#620) docker#621

How to test

cd octi-lab
cp .env.sample .env
docker compose up -d --wait minio
docker compose ps minio   # healthy

Verified locally with Docker 29.5.2 and the exact compose settings of the stack (port mapping left out): the container reaches healthy through /health/ready in a few seconds, and with the .env.sample credentials a bucket create / upload / read / delete round trip works with mc. The OpenCTI and XTM One services of the lab were not started.

Checklist

• I consider the submitted work as finished
• I have signed my commits using GPG key.
• I tested the code for its functionality using different use cases
• I added/update the relevant documentation (either on github or on notion)