MinIO(R) is an object storage server, compatible with Amazon S3 cloud storage service, mainly used for storing unstructured data (such as photos, videos, log files, etc.).

Overview of Bitnami Object Storage based on MinIO(R)

$ docker run --name minio bitnami/minio:latest

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-minio/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DCT). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami MinIO(R) Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 2021, 2021-debian-10, 2021.10.27, 2021.10.27-debian-10-r9, latest (2021/debian-10/Dockerfile)

Subscribe to project updates by watching the bitnami/minio GitHub repo.

The recommended way to get the Bitnami MinIO(R) Docker Image is to pull the prebuilt image from the Docker Hub Registry.

$ docker pull bitnami/minio:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

$ docker pull bitnami/minio:[TAG]

If you wish, you can also build the image yourself.

$ docker build -t bitnami/minio:latest 'https://github.com/bitnami/bitnami-docker-minio.git#master:2021/debian-10'

If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a directory at the /data path.

$ docker run --name minio \
    --publish 9000:9000 \
    --publish 9001:9001 \
    --volume /path/to/minio-persistence:/data \
    bitnami/minio:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  minio:
  ...
    volumes:
      - /path/to/minio-persistence:/data
  ...

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Using Docker container networking, a MinIO(R) server running inside a container can easily be accessed by your application containers.

Containers attached to the same network can communicate with each other using the container name as the hostname.

In this example, we will create a MinIO(R) client container that will connect to the server container that is running on the same docker network as the client.

$ docker network create app-tier --driver bridge

Use the --network app-tier argument to the docker run command to attach the MinIO(R) container to the app-tier network.

$ docker run -d --name minio-server \
    --env MINIO_ACCESS_KEY="minio-access-key" \
    --env MINIO_SECRET_KEY="minio-secret-key" \
    --network app-tier \
    bitnami/minio:latest

Finally we create a new container instance to launch the MinIO(R) client and connect to the server created in the previous step. In this example, we create a new bucket in the MinIO(R) storage server:

$ docker run -it --rm --name minio-client \
    --env MINIO_SERVER_HOST="minio" \
    --env MINIO_SERVER_ACCESS_KEY="minio-access-key" \
    --env MINIO_SERVER_SECRET_KEY="minio-secret-key" \
    --network app-tier \
    bitnami/minio-client \
    mb minio/my-bucket

When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named app-tier. In this example we assume that you want to connect to the MinIO(R) server from your own custom application image which is identified in the following snippet by the service name myapp.

version: '2'

networks:
  app-tier:
    driver: bridge

services:
  minio:
    image: 'bitnami/minio:latest'
    ports:
      - '9000:9000'
      - '9001:9001'
    environment:
      - MINIO_ACCESS_KEY=minio-access-key
      - MINIO_SECRET_KEY=minio-secret-key
    networks:
      - app-tier
  myapp:
    image: 'YOUR_APPLICATION_IMAGE'
    networks:
      - app-tier
    environment:
      - MINIO_SERVER_ACCESS_KEY=minio-access-key
      - MINIO_SERVER_SECRET_KEY=minio-secret-key

IMPORTANT:

1. Please update the YOUR_APPLICATION_IMAGE_ placeholder in the above snippet with your application image
2. In your application container, use the hostname minio to connect to the MinIO(R) server. Use the environment variables MINIO_SERVER_ACCESS_KEY and MINIO_SERVER_SECRET_KEY to configure the credentials to access the MinIO(R) server.

Launch the containers using:

$ docker-compose up -d

MiNIO can be configured via environment variables as detailed at MinIO(R) documentation.

A MinIO(R) Client (mc) is also shipped on this image that can be used to perform administrative tasks as described at the MinIO(R) Client documentation. In the example below, the client is used to obtain the server info:

$ docker run --name minio -d bitnami/minio:latest
$ docker exec minio mc admin info local

or using Docker Compose:

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-minio/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
$ docker-compose exec minio mc admin info local

You can create a series of buckets in the MinIO(R) server during the initialization of the container by setting the environment variable MINIO_DEFAULT_BUCKETS as shown below (policy is optional):

$ docker run --name minio \
    --publish 9000:9000 \
    --publish 9001:9001 \
    --env MINIO_DEFAULT_BUCKETS='my-first-bucket:policy,my-second-bucket' \
    bitnami/minio:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  minio:
  ...
    environment:
      - MINIO_DEFAULT_BUCKETS=my-first-bucket:policy,my-second-bucket
  ...

You can secure the access to MinIO(R) server with TLS as detailed at MinIO(R) documentation.

This image expects the certificates to be mounted at the /certs directory. You can put your key and certificate files on a local directory and mount it in the container as shown below:

$ docker run --name minio \
    --publish 9000:9000 \
    --publish 9001:9001 \
    --volume /path/to/certs:/certs \
    bitnami/minio:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  minio:
  ...
    volumes:
      - /path/to/certs:/certs
  ...

You can configure MinIO(R) in Distributed Mode to setup a highly-available storage system. To do so, the environment variables below must be set on each node:

• MINIO_DISTRIBUTED_MODE_ENABLED: Set it to 'yes' to enable Distributed Mode.
• MINIO_DISTRIBUTED_NODES: List of MinIO(R) nodes hosts. Available separators are ' ', ',' and ';'.
• MINIO_ACCESS_KEY: MinIO(R) server Access Key. Must be common on every node.
• MINIO_SECRET_KEY: MinIO(R) server Secret Key. Must be common on every node.

You can use the Docker Compose below to create an 4-node distributed MinIO(R) setup:

version: '2'

services:
  minio1:
    image: 'bitnami/minio:latest'
    environment:
      - MINIO_ACCESS_KEY=minio-access-key
      - MINIO_SECRET_KEY=minio-secret-key
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio1,minio2,minio3,minio4
      - MINIO_SKIP_CLIENT=yes
  minio2:
    image: 'bitnami/minio:latest'
    environment:
      - MINIO_ACCESS_KEY=minio-access-key
      - MINIO_SECRET_KEY=minio-secret-key
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio1,minio2,minio3,minio4
      - MINIO_SKIP_CLIENT=yes
  minio3:
    image: 'bitnami/minio:latest'
    environment:
      - MINIO_ACCESS_KEY=minio-access-key
      - MINIO_SECRET_KEY=minio-secret-key
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio1,minio2,minio3,minio4
      - MINIO_SKIP_CLIENT=yes
  minio4:
    image: 'bitnami/minio:latest'
    environment:
      - MINIO_ACCESS_KEY=minio-access-key
      - MINIO_SECRET_KEY=minio-secret-key
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio1,minio2,minio3,minio4
      - MINIO_SKIP_CLIENT=yes

MinIO(R) also supports ellipsis syntax ({1..n}) to list the MinIO(R) node hosts, where n is the number of nodes. This syntax is also valid to use multiple drives ({1..m}) on each MinIO(R) node, where n is the number of drives per node. You can use the Docker Compose below to create an 2-node distributed MinIO(R) setup with 2 drives per node:

version: '2'
services:
  minio-0:
    image: 'bitnami/minio:latest'
    volumes:
      - 'minio_0_data_0:/data-0'
      - 'minio_0_data_1:/data-1'
    environment:
      - MINIO_ACCESS_KEY=minio
      - MINIO_SECRET_KEY=miniosecret
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio-{0...1}/data-{0...1}
  minio-1:
    image: 'bitnami/minio:latest'
    volumes:
      - 'minio_1_data_0:/data-0'
      - 'minio_1_data_1:/data-1'
    environment:
      - MINIO_ACCESS_KEY=minio
      - MINIO_SECRET_KEY=miniosecret
      - MINIO_DISTRIBUTED_MODE_ENABLED=yes
      - MINIO_DISTRIBUTED_NODES=minio-{0...1}/data-{0...1}
volumes:
  minio_0_data_0:
    driver: local
  minio_0_data_1:
    driver: local
  minio_1_data_0:
    driver: local
  minio_1_data_1:
    driver: local

Find more information about the Distributed Mode in the MinIO(R) documentation.

MinIO(R) configures the access & secret key during the 1st initialization based on the MINIO_ACCESS_KEY and MINIO_SECRET_KEY environment variables, respetively.

When using persistence, MinIO(R) will reuse the data configured during the 1st initialization by default, ignoring whatever values are set on these environment variables. You can force MinIO(R) to reconfigure the keys based on the environment variables by setting the MINIO_FORCE_NEW_KEYS environment variable to yes:

$ docker run --name minio \
    --publish 9000:9000 \
    --publish 9001:9001 \
    --env MINIO_FORCE_NEW_KEYS="yes" \
    --env MINIO_ACCESS_KEY="new-minio-access-key" \
    --env MINIO_SECRET_KEY="new-minio-secret-key" \
    --volume /path/to/minio-persistence:/data \
    bitnami/minio:latest

The Bitnami MinIO(R) Docker image sends the container logs to the stdout. To view the logs:

$ docker logs minio

or using Docker Compose:

$ docker-compose logs minio

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

To enable HTTP log trace, you can set the environment variable MINIO_HTTP_TRACE to redirect the logs to a specific file as detailed at MinIO(R) documentation.

When setting this environment variable to /opt/bitnami/minio/log/minio.log, the logs will be sent to the stdout.

$ docker run --name minio \
    --publish 9000:9000 \
    --publish 9001:9001 \
    --env MINIO_HTTP_TRACE=/opt/bitnami/minio/log/minio.log \
    bitnami/minio:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  minio:
  ...
    environment:
      - MINIO_HTTP_TRACE=/opt/bitnami/minio/log/minio.log
  ...

Bitnami provides up-to-date versions of MinIO(R), including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.

$ docker pull bitnami/minio:latest

or if you're using Docker Compose, update the value of the image property to bitnami/minio:latest.

Stop the currently running container using the command

$ docker stop minio

or using Docker Compose:

$ docker-compose stop minio

Next, take a snapshot of the persistent volume /path/to/minio-persistence using:

$ rsync -a /path/to/minio-persistence /path/to/minio-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

$ docker rm -v minio

or using Docker Compose:

$ docker-compose rm -v minio

Re-create your container from the new image.

$ docker run --name minio bitnami/minio:latest

or using Docker Compose:

$ docker-compose up minio

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright (c) 2021 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.