MinIO Quickstart Guide
MinIO is a High Performance Object Storage released under Apache License v2.0. It is API compatible with Amazon S3 cloud storage service. Use MinIO to build high performance infrastructure for machine learning, analytics and application data workloads.
docker run -p 9000:9000 \ -e "MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE" \ -e "MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \ minio/minio server /data
docker run -p 9000:9000 \ -e "MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE" \ -e "MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \ minio/minio:edge server /data
NOTE: Docker will not display the default keys unless you start the container with the
-it(interactive TTY) argument. Generally, it is not recommended to use default keys with containers. Please visit MinIO Docker quickstart guide for more information here
Install minio packages using Homebrew
brew install minio/stable/minio minio server /data
NOTE: If you previously installed minio using
brew install miniothen it is recommended that you reinstall minio from
minio/stable/minioofficial repo instead.
brew uninstall minio brew install minio/stable/minio
|Apple macOS||64-bit Intel||https://dl.min.io/server/minio/release/darwin-amd64/minio|
chmod 755 minio ./minio server /data
wget https://dl.min.io/server/minio/release/linux-amd64/minio chmod +x minio ./minio server /data
wget https://dl.min.io/server/minio/release/linux-ppc64le/minio chmod +x minio ./minio server /data
minio.exe server D:\Photos
pkg install minio sysrc minio_enable=yes sysrc minio_disks=/home/user/Photos service minio start
Install from Source
GO111MODULE=on go get github.com/minio/minio
Allow port access for Firewalls
By default MinIO uses the port 9000 to listen for incoming connections. If your platform blocks the port by default, you may need to enable access to the port.
For hosts with ufw enabled (Debian based distros), you can use
ufw command to allow traffic to specific ports. Use below command to allow access to port 9000
ufw allow 9000
Below command enables all incoming traffic to ports ranging from 9000 to 9010.
ufw allow 9000:9010/tcp
For hosts with firewall-cmd enabled (CentOS), you can use
firewall-cmd command to allow traffic to specific ports. Use below commands to allow access to port 9000
This command gets the active zone(s). Now, apply port rules to the relevant zones returned above. For example if the zone is
firewall-cmd --zone=public --add-port=9000/tcp --permanent
permanent makes sure the rules are persistent across firewall start, restart or reload. Finally reload the firewall for changes to take effect.
For hosts with iptables enabled (RHEL, CentOS, etc), you can use
iptables command to enable all traffic coming to specific ports. Use below command to allow
access to port 9000
iptables -A INPUT -p tcp --dport 9000 -j ACCEPT service iptables restart
Below command enables all incoming traffic to ports ranging from 9000 to 9010.
iptables -A INPUT -p tcp --dport 9000:9010 -j ACCEPT service iptables restart
Test using MinIO Browser
MinIO Server comes with an embedded web based object browser. Point your web browser to http://127.0.0.1:9000 ensure your server has started successfully.
Test using MinIO Client
mc provides a modern alternative to UNIX commands like ls, cat, cp, mirror, diff etc. It supports filesystems and Amazon S3 compatible cloud storage services. Follow the MinIO Client Quickstart Guide for further instructions.
When deployed on a single drive, MinIO server lets clients access any pre-existing data in the data directory. For example, if MinIO is started with the command
minio server /mnt/data, any pre-existing data in the
/mnt/data directory would be accessible to the clients.
The above statement is also valid for all gateway backends.
MinIO server supports rolling upgrades, i.e. you can update one MinIO instance at a time in a distributed cluster. This allows upgrades with no downtime. Upgrades can be done manually by replacing the binary with the latest release and restarting all servers in a rolling fashion. However, we recommend all our users to use
mc admin update from the client. This will update all the nodes in the cluster simultaneously and restart them, as shown in the following command from the MinIO client (mc):
mc admin update <minio alias, e.g., myminio>
NOTE: some releases might not allow rolling upgrades, this is always called out in the release notes and it is generally advised to read release notes before upgrading. In such a situation
mc admin updateis the recommended upgrading mechanism to upgrade all servers at once.
Important things to remember during MinIO upgrades
mc admin updatewill only work if the user running MinIO has write access to the parent directory where the binary is located, for example if the current binary is at
/usr/local/bin/minio, you would need write access to
mc admin updateupdates and restarts all servers simultaneously, applications would retry and continue their respective operations upon upgrade.
mc admin updateis disabled in kubernetes/container environments, container environments provide their own mechanisms to rollout of updates.
- In the case of federated setups
mc admin updateshould be run against each cluster individually. Avoid updating
mcto any new releases until all clusters have been successfully updated.
- If using
kesas KMS with MinIO, just replace the binary and restart
kesmore information about
kescan be found herex
- If using Vault as KMS with MinIO, ensure you have followed the Vault upgrade procedure outlined here: https://www.vaultproject.io/docs/upgrading/index.html
- If using etcd with MinIO for the federation, ensure you have followed the etcd upgrade procedure outlined here: https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrading-etcd.md
- MinIO Erasure Code QuickStart Guide
mcwith MinIO Server
aws-cliwith MinIO Server
s3cmdwith MinIO Server
minio-goSDK with MinIO Server
- The MinIO documentation website
Contribute to MinIO Project
Please follow MinIO Contributor's Guide
Use of MinIO is governed by the Apache 2.0 License found at LICENSE.
There is no documentation for this package.
Package browser Code generated by go-bindata.
|Package browser Code generated by go-bindata.|
Package cmd This file implements helper functions to validate AWS Signature Version '4' authorization header.
|Package cmd This file implements helper functions to validate AWS Signature Version '4' authorization header.|
Package crypto implements AWS S3 related cryptographic building blocks for implementing Server-Side-Encryption (SSE-S3) and Server-Side-Encryption with customer provided keys (SSE-C).
|Package crypto implements AWS S3 related cryptographic building blocks for implementing Server-Side-Encryption (SSE-S3) and Server-Side-Encryption with customer provided keys (SSE-C).|
Package cgroup implements parsing for all the cgroup categories and functionality in a simple way.
|Package cgroup implements parsing for all the cgroup categories and functionality in a simple way.|
Package console implements console printing helpers
|Package console implements console printing helpers|
Package csv reads and writes comma-separated values (CSV) files.
|Package csv reads and writes comma-separated values (CSV) files.|
Package ioutil implements some I/O utility functions which are not covered by the standard library.
|Package ioutil implements some I/O utility functions which are not covered by the standard library.|
Package licverifier implements a simple library to verify MinIO Subnet license keys.
|Package licverifier implements a simple library to verify MinIO Subnet license keys.|
Package lock - implements filesystem locking wrappers around an open file descriptor.
|Package lock - implements filesystem locking wrappers around an open file descriptor.|
Package mimedb is a database of file extension to mime content-type.
|Package mimedb is a database of file extension to mime content-type.|
Package trie implements a simple trie tree for minio server/tools borrows idea from - https://godoc.org/golang.org/x/text/internal/triegen.
|Package trie implements a simple trie tree for minio server/tools borrows idea from - https://godoc.org/golang.org/x/text/internal/triegen.|