readystack/minio repository overview

⁠MinIO

readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/minio/recipe⁠
• Upstream source at this release's pinned commit (RELEASE.2025-10-15T17-29-55Z): https://github.com/minio/minio/tree/9e49d5e7a648f00e26f2246f4dc28e6b07f8c84a⁠
• Product page: https://readystack.dev/products/minio⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/minio⁠
• Release history (JSON): https://readystack.dev/api/releases/minio⁠
• Defect record: https://readystack.dev/defects.html?product=minio⁠
• Today's scan: https://readystack.dev/products/minio#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=minio⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/minio/minio RELEASE.2025-10-15T17-29-55Z (AGPL-3.0), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: Teams who need object storage on their own hardware for backups, analytics data and application files.

Why: MinIO is open-source object storage compatible with an established cloud object-storage API, so existing tools and applications written for that API can store data on your own servers.

Use case: A team's backup software and data pipelines are written for cloud object storage, but the data must stay on site. They point those tools at MinIO on their own servers and keep their backups and datasets in buckets there.

About the upstream project, written from its own description: https://github.com/minio/minio⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:1a7336d989e14a5c7fd4be67c96e4eb4c5756821ba44f33c507ef325bbc6ae66 on 2026-11-11.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/minio⁠
• ReadyStack release check — passed at release on 2026-11-11: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:1a7336d989e14a5c7fd4be67c96e4eb4c5756821ba44f33c507ef325bbc6ae66; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (minio).
• Built from source by ReadyStack; the web Console's compiled React frontend is the prebuilt bundle that ships inside the github.com/minio/console Go module (//go:embed build/*), vendored with the Go dependencies; it is not built here.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10

# ✗ unsupported (do not pull)
docker pull readystack/minio:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container, single static Go binary (CGO-free), foreground process. S3-compatible OBJECT STORAGE: objects + metadata persisted on the local filesystem under /data (internal state under /data/.minio.sys). NO relational/SQL database. Embeds and serves a web Console (an object browser) on port 9001. The image IS the complete running instance (no docker-compose, no Kubernetes, no external DB). The entrypoint, /usr/local/bin/readystack-entrypoint.sh, works out the root password MinIO will use (from MINIO_ROOT_PASSWORD, a MINIO_ROOT_PASSWORD_FILE secret or MINIO_CONFIG_ENV_FILE), exits 1 if it is unset, blank or minioadmin (and also on other unusable credential input, for example a root user or password that starts with "env", a *_FILE secret or MINIO_CONFIG_ENV_FILE naming a missing or unreadable file, or an empty *_FILE secret), and then runs minio with the default arguments server /data --address :9000 --console-address :9001, which arguments after the image name replace.

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create minio.env with install -m 600 /dev/null minio.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# The root credential (access key and secret key); both are needed at every start.
MINIO_ROOT_USER=YOUR_ACCESS_KEY
MINIO_ROOT_PASSWORD=YOUR_STRONG_SECRET

docker run -d --name minio -p 9000:9000 -p 9001:9001 --env-file ./minio.env -v minio-data:/data readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10

minio is this command's own container name. MINIO_ROOT_USER and MINIO_ROOT_PASSWORD in minio.env are required at every start: without a root password, or with the password minioadmin, the container exits at once with a readystack: message. Boot is fast (about 2 seconds to a 200 on /minio/health/live, tested). Sign in to the Console at http://:9001 with the same access key and secret key, or drive the S3 API on :9000 with a sig-v4 client (curl --aws-sigv4 or an AWS SDK; mc is not in this image). Arguments after readystack/minio:RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10 replace the default server /data --address :9000 --console-address :9001. ReadyStack ships no Compose file for this image.

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r10 — the build raises Go-module dependency versions in go.mod and go.sum to fixed, upstream-published releases (security updates; no MinIO source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/minio/RELEASE.2025-10-15T17-29-55Z/minio-RELEASE.2025-10-15T17-29-55Z-readystack.patch⁠
• RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r9 — the build raises Go-module dependency versions in go.mod and go.sum to fixed, upstream-published releases (security updates; no MinIO source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/minio/RELEASE.2025-10-15T17-29-55Z/minio-RELEASE.2025-10-15T17-29-55Z-readystack.patch⁠
• RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r8 — the build raises Go-module dependency versions in go.mod and go.sum to fixed, upstream-published releases (security updates; no MinIO source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/minio/RELEASE.2025-10-15T17-29-55Z/minio-RELEASE.2025-10-15T17-29-55Z-readystack.patch⁠
• RELEASE.2025-10-15T17-29-55Z-CE-ubuntu24.04-r7 — the build raises Go-module dependency versions in go.mod and go.sum to fixed, upstream-published releases (security updates; no MinIO source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/minio/RELEASE.2025-10-15T17-29-55Z/minio-RELEASE.2025-10-15T17-29-55Z-readystack.patch⁠

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/minio⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:b5a072d9c16b2060f4fc6bd2afed1632769df1f5e179992af2525515e0d3dde4 on 2026-11-11.

— ReadyStack · readystack.dev