zeekay
6b0f2d88ff
- Replace all MinIO brand references with S3 in docs, helm charts, and comments - Replace quay.io/minio images with ghcr.io/hanzoai/s3 and ghcr.io/hanzos3/* - Replace min.io domains: docs→docs.hanzo.ai, dl→dl.hanzo.space, play→play.hanzo.space - Replace slack.min.io with hanzo.ai/discord - Replace subnet.min.io with subnet.hanzo.ai - Update Makefile REPO to ghcr.io/hanzoai - Update helm values: mc image, OIDC clientId, service account name - Update Go source user-facing URLs and messages - Fix test configs and grafana dashboard descriptions
3.2 KiB
Deploy S3 on Docker Compose 
Docker Compose allows defining and running single host, multi-container Docker applications.
With Compose, you use a Compose file to configure S3 services. Then, using a single command, you can create and launch all the Distributed S3 instances from your configuration. Distributed S3 instances will be deployed in multiple containers on the same host. This is a great way to set up development, testing, and staging environments, based on Distributed S3.
1. Prerequisites
- Familiarity with Docker Compose.
- Docker installed on your machine. Download the relevant installer from here.
2. Run Distributed S3 on Docker Compose
To deploy Distributed S3 on Docker Compose, please download docker-compose.yaml and nginx.conf to your current working directory. Note that Docker Compose pulls the S3 Docker image, so there is no need to build S3 from source when using Docker. For non-Docker deployments, S3 community edition is now source-only and can be installed via go install github.com/hanzoai/s3@latest. Then run one of the below commands
GNU/Linux and macOS
docker-compose pull
docker-compose up
or
docker stack deploy --compose-file docker-compose.yaml minio
Windows
docker-compose.exe pull
docker-compose.exe up
or
docker stack deploy --compose-file docker-compose.yaml minio
Distributed instances are now accessible on the host using the S3 CLI on port 9000 and the S3 Web Console on port 9001. Proceed to access the Web browser at http://127.0.0.1:9001/. Here 4 S3 server instances are reverse proxied through Nginx load balancing.
Notes
-
By default the Docker Compose file uses the Docker image for latest S3 server release. You can change the image tag to pull a specific S3 Docker image.
-
There are 4 minio distributed instances created by default. You can add more S3 services (up to total 16) to your S3 Compose deployment. To add a service
- Replicate a service definition and change the name of the new service appropriately.
- Update the command section in each service.
- Add a new S3 server instance to the upstream directive in the Nginx configuration file.
Read more about distributed S3 here.