Tools [active]
MinIO Docker Setup
An interactive installer and manager for a self-hosted, S3-compatible object store on Ubuntu or Debian, using the maintained PGSTY Silo fork of MinIO.
- Tech
- Bash · Docker Compose · MinIO / Silo · systemd
Problem
The upstream minio/minio repository is archived and no longer publishes community Docker images, so minio/minio:latest is a frozen build without security fixes. Setting up a replacement by hand also means writing .env and compose files, buckets, users, and policies every time.
What it does
- Installs through an interactive menu, or runs single commands for automation. No manual editing of
.envordocker-compose.yml. - Uses PGSTY Silo, a maintained, drop-in compatible MinIO fork. It looks up the newest stable release, checks that its image is published, and pins that exact tag.
- Creates buckets, an application user with a least-privilege policy, and optional public read access per bucket.
- Backup and restore, lifecycle commands, health checks, and public URL settings for use behind a reverse proxy.
- Optional scheduled update check (systemd timer) in
checkorapplymode.applybacks up first and rolls back automatically if the new container is unhealthy.
Usage
git clone https://github.com/raqolbi/minio-docker-setup.git minio-setup
cd minio-setup
chmod +x setup.sh
./setup.sh # opens the menu; choose 1) Install MinIO
Common commands:
./setup.sh status
./setup.sh backup
./setup.sh check-update
./setup.sh update # backup + upgrade + rollback on failure
./setup.sh auto-update enable
Notes
- Requires Ubuntu 22.04+ or Debian 12+ with Docker Compose v2.
mcruns inside the container, so credentials never appear on the host command line.- Update checks need outbound HTTPS to
api.github.comand Docker Hub.