Self-host MinIO with Levelrail

Verified

S3-compatible object storage you run yourself, with a built-in web console.

  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host MinIO

  1. Pull the images

    One image is pulled on your server.

    Show images
    • quay.io/minio/aistor/minio:RELEASE.2026-09-19T17-05-25Z.hotfix.4ef74f03d6f2
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on ports 9000, 9001.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

MinIO requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 tested
Ports
9000, 9001
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Verified. Verified on arm64 with image tag RELEASE.2026-09-19T17-05-25Z.hotfix.4ef74f03d6f2. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes ports 9000, 9001 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then MinIO. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the MinIO docs page.

Deploy MinIO your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy MinIO from the CLI

levelrail-cli templates deploy minio --name my-minio

Deploy MinIO with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/minio/deploy

MinIO configuration

MinIO services

ServiceImagePortsVolumes
minio quay.io/minio/aistor/minio:RELEASE.2026-09-19T17-05-25Z.hotfix.4ef74f03d6f2 9000, 9001 minio_data -> /data

MinIO environment variables

VariableServiceValue
MINIO_ROOT_PASSWORD minio Generated at deploy
MINIO_ROOT_USER minio Generated at deploy

Ports and volumes

Ports
9000, 9001
Volumes
1 named mount: minio_data -> /data

MinIO FAQ

How much memory does MinIO need?

The catalog lists about 512 MiB of memory for MinIO.

Does MinIO run on arm64?

For MinIO, arm64 is tested; amd64 is image published.

Does MinIO need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does MinIO use?

MinIO listens on ports 9000 and 9001 inside the stack.

Where does MinIO keep its data?

In a named volume: minio_data mounted at /data.

Can I deploy MinIO on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id minio for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image quay.io/minio/aistor/minio:RELEASE.2026-09-19T17-05-25Z.hotfix.4ef74f03d6f2 is what you deploy there.

levelrail-cli templates deploy minio --name my-minio