Portainer Templates logo

Portainer Templates

Minio (container) Minio (container)

Storage

A distributed object storage server built for cloud applications and devops

Configuration

Type
Container
Platform
linux
Image
quay.io/minio/minio:latest
Command
server /data --console-address ':9001'
Ports
9000/tcp9001/tcp
Volumes
/data/root/.minio
Env vars
MINIO_ROOT_USER=''MINIO_ROOT_PASSWORD=''

Template by portainer

Report issue

Standalone Install

Select an install method, to see config/commands for deploying Minio (container)

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Minio (container), fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Serve Minio (container) on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying minio-container.example.com to http://minio-container:9000

Add this to your Caddyfile

minio-container.example.com {
	reverse_proxy http://minio-container:9000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 9000/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull quay.io/minio/minio:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Required settings are blank

MINIO_ROOT_USER, MINIO_ROOT_PASSWORD have no default value, and the app may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Minio (container) runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Minio (container) needs bundled into one download. This template pulls quay.io/minio/minio:latest, which Docker fetches once and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Minio (container)'s comes from Quay, published by minio.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 9000, published on a random host port
  • 9001, published on a random host port

Volumes

A volume is where Minio (container) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /data as a volume Docker manages for you
  • /root/.minio as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Minio (container) takes 2 of them, and 2 need a value before it'll start properly:

  • MINIO_ROOT_USER, needs a value. Root user
  • MINIO_ROOT_PASSWORD, needs a value. Root password

Networking

Nothing custom is set, so Minio (container) sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Startup command

The command is what runs the moment the container starts. This template sets its own, server /data --console-address ':9001', in place of the image's default.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Minio (container) up. Add the template list to Portainer once, then deploying Minio (container) is a click rather than a wall of config.