Silo pgsty/silo:latest https://hub.docker.com/r/pgsty/silo bridge sh false https://github.com/junkerderprovinz/unraid-apps/blob/main/silo/README.md https://forums.unraid.net/topic/198811-support-junkerderprovinz-unraid-apps/ https://github.com/pgsty/silo PGSTY Silo is an S3-compatible object store: a maintained fork of the open-source MinIO server, published by Pigsty after MinIO stopped distributing its community edition. The S3 API, the MINIO_* settings and the on-disk format are unchanged; Pigsty adds security fixes and keeps the full web console. Silo is AGPL-3.0, and this template runs the official image. Why this template exists: started as it comes, the image prints its help text and exits, because it needs to be told to serve a folder. The template starts it as a server on /data with the console on a fixed port, runs it as 99:100 so the files it writes on your share belong to nobody:users instead of root, and makes the credentials required fields, because left empty Silo falls back to the well-known minioadmin:minioadmin account. Ports: 9000 is the S3 endpoint every client connects to. 9001 is the web console. Coming from pgsty/minio or another MinIO container: point Data at the old data folder and keep the same credentials. If that container ran as root, run chown -R nobody:users on the folder first, or Silo stops at startup with "file access denied". The README has the details. Backup: Cloud: Network:Web Tools:Utilities http://[IP]:[PORT:9001] https://raw.githubusercontent.com/junkerderprovinz/unraid-apps/main/silo/silo.xml https://raw.githubusercontent.com/junkerderprovinz/unraid-apps/main/silo/icon.png --restart=unless-stopped --user 99:100 server /data --console-address ":9001" If this template helps you, consider buying me a coffee. https://buymeacoffee.com/junkerderprovinz Set a Root User and a Root Password below, at least 8 characters for the password. Left empty, Silo starts with the default account minioadmin:minioadmin, which everyone knows. 9000 9001 /mnt/user/appdata/silo/data