Skip to content

Latest commit

 

History

History
132 lines (80 loc) · 3.92 KB

running-minio-in-docker.md

File metadata and controls

132 lines (80 loc) · 3.92 KB
Raw

How to run Minio in Docker? Gitter

1. Prerequisites

2. Steps

Add a local alias for docker (optional)

I am adding an alias to my local bashrc file to avoid typing sudo along with running docker command.

alias docker="sudo /usr/bin/docker"

Fetching Minio image from repository & running Minio in docker.

$ docker run -p 9000:9000 minio/minio:latest

Endpoint:  http://10.0.0.10:9000  http://127.0.0.1:9000  http://172.17.0.1:9000
AccessKey: USWUXHGYZQYFYFFIT3RE
SecretKey: MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
Region:    us-east-1

Browser Access:
  http://10.0.0.10:9000  http://127.0.0.1:9000  http://172.17.0.1:9000

Command-line Access: https://docs.minio.io/docs/minio-client-quickstart-guide
  $ mc config host add myminio http://10.0.0.10:9000 USWUXHGYZQYFYFFIT3RE MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03

Object API (Amazon S3 compatible):
  Go:         https://docs.minio.io/docs/golang-client-quickstart-guide
  Java:       https://docs.minio.io/docs/java-client-quickstart-guide
  Python:     https://docs.minio.io/docs/python-client-quickstart-guide
  JavaScript: https://docs.minio.io/docs/javascript-client-quickstart-guide

Add Minio configuration to mc

$ mc config host add localhost http://localhost:9000 USWUXHGYZQYFYFFIT3RE MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03

Play with Minio server

$ mc mb localhost/newbucket
Bucket created successfully ‘localhost/newbucket’.

$ mc mb localhost/mybucket
Bucket created successfully ‘localhost/mybucket’.

Persist Minio configs

Running Minio container

$ docker ps
CONTAINER ID        IMAGE                COMMAND                CREATED             STATUS              PORTS                    NAMES
51e3a48d209a        minio/minio:latest   "/minio server /expo   22 hours ago        Up 22 hours         0.0.0.0:9000->9000/tcp   fervent_shockley

$ docker commit 51e3a48d209a minio/my-minio
fcc98afd0b4da9340b3e635d73a82088e7224798b3467138840b997959af4520

$ docker stop 51e3a48d209a
51e3a48d209a

NOTE: Replace the container id with your own.

Create a data volume container

$ docker create -v /export --name minio-export minio/my-minio /bin/true
4e466c4572b96cc16a619f6e13155657745aa653b1857929100f1a8208a58da8

$ docker run -p 9000:9000 --volumes-from minio-export --name minio1 minio/my-minio

Endpoint:  http://10.0.0.10:9000  http://127.0.0.1:9000  http://172.17.0.1:9000
AccessKey: USWUXHGYZQYFYFFIT3RE
SecretKey: MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
Region:    us-east-1

Browser Access:
  http://10.0.0.10:9000  http://127.0.0.1:9000  http://172.17.0.1:9000

Command-line Access: https://docs.minio.io/docs/minio-client-quickstart-guide
  $ mc config host add myminio http://10.0.0.10:9000 USWUXHGYZQYFYFFIT3RE MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03

Object API (Amazon S3 compatible):
  Go:         https://docs.minio.io/docs/golang-client-quickstart-guide
  Java:       https://docs.minio.io/docs/java-client-quickstart-guide
  Python:     https://docs.minio.io/docs/python-client-quickstart-guide
  JavaScript: https://docs.minio.io/docs/javascript-client-quickstart-guide

Test the Persist feature

We created a few buckets in our previous Minio server. Let us see if they still exists.

$ mc ls localhost
[2016-01-20 14:25:56 IST]     0B mybucket/
[2016-01-21 12:59:52 IST]     0B newbucket/

They are very much intact, it clearly means we were able to store the Minio docker image.