minio

A high-performance, S3-compatible object storage server designed for cloud-native and edge environments.

ceph/ceph
rook/ceph
amazon/aws-cli
minio/mc

What is minio image?

The minio image packages MinIO, an S3-compatible object storage system built for high throughput, low latency, and scalability. MinIO implements the Amazon S3 API, making it a drop-in replacement for applications expecting S3-style object storage, including analytics systems, ML pipelines, logging platforms, and distributed applications.

MinIO supports multi-tenant buckets, erasure coding, encryption, identity management, versioning, replication, and tiering. It is designed for Kubernetes, bare-metal clusters, and edge deployments, offering consistent performance regardless of the underlying hardware. The container image can be used for both single-node development environments and full distributed clusters supporting petabyte-scale workloads.

Its popularity in containerized infrastructure comes from its simplicity, strong performance characteristics, and compatibility with a wide range of cloud-native tools and data processing frameworks.

How to use this image

The minio image can run as a standalone S3-compatible server or as part of a distributed cluster. Configuration is typically driven by environment variables.

Run a standalone MinIO server:

docker run -d -p 9000:9000 -p 9001:9001 \ -e MINIO_ROOT_USER=minio \ -e MINIO_ROOT_PASSWORD=minio123 \ minio/minio server /data --console-address ":9001"

Use MinIO Client (mc) to create a bucket:

docker run --rm minio/mc \ mc alias set local http://host.docker.internal:9000 minio minio123
docker run --rm minio/mc \ mc mb local/mybucket

Distributed MinIO cluster (example):

docker run -d --name minio1 minio/minio server \ http://minio{1...4}/data --console-address ":9001"

MinIO exposes:

  • 9000 — S3 API
  • 9001 — Web console

Logs are written to stdout and can be collected via container logging systems or centralized log pipelines.

Image variants

Published under minio/minio, the image is available in several variants:

  • minio/minio:latest
    Tracks the latest stable release of MinIO Server.
    Best for development or testing.
  • minio/minio: MinIO uses date-based versioning (e.g., RELEASE.2024-05-01T01-07-30Z). Strongly recommended for production to ensure reproducibility.
  • minio/mc
    The MinIO Client image (not the server), used for managing buckets, policies, and data operations.
    Often deployed alongside MinIO Server for automation.

MinIO images update frequently with security patches and enhancements. Pinning to explicit release tags is recommended to avoid unexpected changes.

Interested in base images that start and stay clean?