1.8 KiB

Raw Blame History

Minio Docker Quickstart Guide

1. Test Minio Docker Container

Minio generates new access and secret keys each time you run this command. Container state is lost after you end this session. This mode is only intended for testing purpose.


docker run -p 9000:9000 minio/minio /export

2. Run One Minio Docker Container

Minio container requires a persistent volume to store configuration and application data. Following command maps local persistent directories from the host OS to virtual config ~/.minio and export /export directories.


docker run -p 9000:9000 --name minio1 \
  -v /mnt/export/minio1:/export \
  -v /mnt/config/minio1:/root/.minio \
  minio/minio /export

3. Custom Access and Secret Keys

To override Minio's auto-generated keys, you may pass secret and access keys explicitly as environment variables. Minio server also allows regular strings as access and secret keys.


docker run -p 9000:9000 --name minio1 \
  -e "MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE" \
  -e "MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \
  -v /mnt/export/minio1:/export \
  -v /mnt/config/minio1:/root/.minio \
  minio/minio /export

4. Run Minio in clustered mode

Let's consider that we need to run 4 minio servers inside different docker containers. The docker-compose.yml file in the root of the project sets this up using the docker-compose tool.

Start Minio docker instances

From the root directory of the project, run:

$ docker-compose up

Each instance's minio web-server is accessible on the host at ports 9001 through 9004, so you may access the first one at http://localhost:9001/

1.8 KiB Raw Blame History