MyFavMirrors
/
minio
mirror of https://github.com/minio/minio.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
minio/docs/orchestration/docker-compose/docker-compose.yaml

83 lines
2.2 KiB
YAML
Raw Normal View History

Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
version: '3.7'
Add docker-compose file to run Minio in distributed mode (#2606) Serves as a starting point to run a Minio cluster using Docker. The file can be used as configuration for the docker-compose tool to start 4 Minio servers in distributed mode. * Add a docker-compose.yml file to run 4 minio server instances in distributed mode * Update Docker.md with command to use the file
2016-09-01 19:35:26 -04:00
# starts 4 docker containers running minio server instances. Each
# minio server's web interface will be accessible on the host at port
# 9001 through 9004.
services:
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
minio1:
Update yaml files to latest version RELEASE.2019-08-21T19-40-07Z
2019-08-21 15:46:01 -04:00
image: minio/minio:RELEASE.2019-08-21T19-40-07Z
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
volumes:
- data1:/data
ports:
- "9001:9000"
environment:
MINIO_ACCESS_KEY: minio
MINIO_SECRET_KEY: minio123
command: server http://minio1/data http://minio2/data http://minio3/data http://minio4/data
healthcheck:
test: ["CMD", "curl", "-f", "http://minio1:9000/minio/health/live"]
interval: 1m30s
timeout: 20s
retries: 3
start_period: 3m
minio2:
Update yaml files to latest version RELEASE.2019-08-21T19-40-07Z
2019-08-21 15:46:01 -04:00
image: minio/minio:RELEASE.2019-08-21T19-40-07Z
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
volumes:
- data2:/data
ports:
- "9002:9000"
environment:
MINIO_ACCESS_KEY: minio
MINIO_SECRET_KEY: minio123
command: server http://minio1/data http://minio2/data http://minio3/data http://minio4/data
healthcheck:
test: ["CMD", "curl", "-f", "http://minio2:9000/minio/health/live"]
interval: 1m30s
timeout: 20s
retries: 3
start_period: 3m
minio3:
Update yaml files to latest version RELEASE.2019-08-21T19-40-07Z
2019-08-21 15:46:01 -04:00
image: minio/minio:RELEASE.2019-08-21T19-40-07Z
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
volumes:
- data3:/data
ports:
- "9003:9000"
environment:
MINIO_ACCESS_KEY: minio
MINIO_SECRET_KEY: minio123
command: server http://minio1/data http://minio2/data http://minio3/data http://minio4/data
healthcheck:
test: ["CMD", "curl", "-f", "http://minio3:9000/minio/health/live"]
interval: 1m30s
timeout: 20s
retries: 3
start_period: 3m
minio4:
Update yaml files to latest version RELEASE.2019-08-21T19-40-07Z
2019-08-21 15:46:01 -04:00
image: minio/minio:RELEASE.2019-08-21T19-40-07Z
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism.
2019-08-17 15:44:04 -04:00
volumes:
- data4:/data
ports:
- "9004:9000"
environment:
MINIO_ACCESS_KEY: minio
MINIO_SECRET_KEY: minio123
command: server http://minio1/data http://minio2/data http://minio3/data http://minio4/data
healthcheck:
test: ["CMD", "curl", "-f", "http://minio4:9000/minio/health/live"]
interval: 1m30s
timeout: 20s
retries: 3
start_period: 3m
Update docker-compose sample file to use local volume driver so data (#4937) persists even after Minio container is stopped/deleted
2017-09-19 15:43:45 -04:00
## By default this config uses default local driver,
## For custom volumes replace with volume driver configuration.
volumes:
data1:
data2:
data3:
data4: