You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Anis Elleuch ae731d232f
trace: Reorder http/trace maxClients wrapping for correct tracing (#11202)
4 years ago
.github xl: Always set root disk to true in test environment (#11094) 4 years ago
browser lifecycle improvements and additional debug logging (#11096) 4 years ago
buildscripts fix: refactor locks to apply them uniquely per node (#11052) 4 years ago
cmd trace: Reorder http/trace maxClients wrapping for correct tracing (#11202) 4 years ago
dockerscripts Remove alpine based image in favour or RedHat UBI (#11006) 4 years ago
docs Fix caddy project url (#11198) 4 years ago
mint fix testMultipartUploadFailure to properly cleanup (#11137) 4 years ago
pkg fix: docs typos and keywords 4 years ago
.dockerignore Add a basic .dockerignore file to reduce docker context in `make docker` (#8282) 5 years ago
.gitignore Remove healthcheck script for Docker image (#8095) 5 years ago
.golangci.yml use argon2 with sync.Pool for better memory management (#11019) 4 years ago
.goreleaser.yml add minisign verification for container builds (#10115) 4 years ago
.mailmap Replace Minio refs in docs with MinIO and links (#7494) 6 years ago
.nancy-ignore remove ignoring incorrect CVE (#10597) 4 years ago
CONTRIBUTING.md fix: docs remove goreportcard, its deprecated 5 years ago
CREDITS update gocredits with new updated dependencies 4 years ago
Dockerfile Remove alpine based image in favour or RedHat UBI (#11006) 4 years ago
Dockerfile.cicd avoid updating nsswitch.conf for redhat UBI images (#11056) 4 years ago
Dockerfile.dev avoid updating nsswitch.conf for redhat UBI images (#11056) 4 years ago
Dockerfile.dev.browser avoid updating nsswitch.conf for redhat UBI images (#11056) 4 years ago
Dockerfile.mint migrate mint tests to latest versions (#9424) 5 years ago
Dockerfile.release update release Dockerfile string 4 years ago
LICENSE Initial commit 10 years ago
Makefile fix: refactor locks to apply them uniquely per node (#11052) 4 years ago
NOTICE cleanup unneeded files, update credits (#8858) 5 years ago
README.md fix: README with missing word (#11035) 4 years ago
README_zh_CN.md update docs to indicate go1.14 is minimum 4 years ago
SECURITY.md Fix SECURITY.md format and newlines 5 years ago
VULNERABILITY_REPORT.md add vulnerability report policy (#11084) 4 years ago
code_of_conduct.md cleanup unneeded files, update credits (#8858) 5 years ago
docker-buildx.sh ubi-minimal doesn't support arm32, remove from build manifest 4 years ago
go.mod Update yaml files to latest version RELEASE.2020-12-23T02-24-12Z 4 years ago
go.sum Update yaml files to latest version RELEASE.2020-12-23T02-24-12Z 4 years ago
main.go update docs to indicate go1.14 is minimum 4 years ago
minio.spec fix: update RPM spec using rpmbuild (#10979) 4 years ago
ruleguard.rules.go fix: IAM store fallback to list users and policies from disk (#10787) 4 years ago
staticcheck.conf Add response header timeouts (#9170) 5 years ago

README.md

MinIO Quickstart Guide

Slack Docker Pulls

MinIO

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 Container

Stable

docker run -p 9000:9000 \
  -e "MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE" \
  -e "MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \
  minio/minio server /data

Edge

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

macOS

Install minio packages using Homebrew

brew install minio/stable/minio
minio server /data

NOTE: If you previously installed minio using brew install minio then it is recommended that you reinstall minio from minio/stable/minio official repo instead.

brew uninstall minio
brew install minio/stable/minio

Binary Download

Platform Architecture URL
Apple macOS 64-bit Intel https://dl.min.io/server/minio/release/darwin-amd64/minio
chmod 755 minio
./minio server /data

GNU/Linux

Binary Download

Platform Architecture URL
GNU/Linux 64-bit Intel https://dl.min.io/server/minio/release/linux-amd64/minio
wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x minio
./minio server /data
Platform Architecture URL
GNU/Linux ppc64le https://dl.min.io/server/minio/release/linux-ppc64le/minio
wget https://dl.min.io/server/minio/release/linux-ppc64le/minio
chmod +x minio
./minio server /data

Microsoft Windows

Binary Download

Platform Architecture URL
Microsoft Windows 64-bit https://dl.min.io/server/minio/release/windows-amd64/minio.exe
minio.exe server D:\Photos

FreeBSD

Port

Install minio packages using pkg, MinIO doesn't officially build FreeBSD binaries but is maintained by FreeBSD upstream here.

pkg install minio
sysrc minio_enable=yes
sysrc minio_disks=/home/user/Photos
service minio start

Install from Source

Source installation is only intended for developers and advanced users. If you do not have a working Golang environment, please follow How to install Golang. Minimum version required is go1.15

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.

ufw

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

firewall-cmd

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

firewall-cmd --get-active-zones

This command gets the active zone(s). Now, apply port rules to the relevant zones returned above. For example if the zone is public, use

firewall-cmd --zone=public --add-port=9000/tcp --permanent

Note that permanent makes sure the rules are persistent across firewall start, restart or reload. Finally reload the firewall for changes to take effect.

firewall-cmd --reload

iptables

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 to ensure your server has started successfully.

Screenshot

Test using MinIO Client mc

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.

Pre-existing data

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.

Upgrading MinIO

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 update is the recommended upgrading mechanism to upgrade all servers at once.

Important things to remember during MinIO upgrades

  • mc admin update will 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 /usr/local/bin.
  • mc admin update updates and restarts all servers simultaneously, applications would retry and continue their respective operations upon upgrade.
  • mc admin update is disabled in kubernetes/container environments, container environments provide their own mechanisms to rollout of updates.
  • In the case of federated setups mc admin update should be run against each cluster individually. Avoid updating mc to any new releases until all clusters have been successfully updated.
  • If using kes as KMS with MinIO, just replace the binary and restart kes more information about kes can be found here
  • 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

Explore Further

Contribute to MinIO Project

Please follow MinIO Contributor's Guide

License

Use of MinIO is governed by the Apache 2.0 License found at LICENSE.