mirror of
https://github.com/bitnami/containers.git
synced 2026-10-17 14:21:32 +02:00
[bitnami/minio] Release 2025.10.15-debian-12-r11 (#92018)
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
@@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
|
||||
ARG TARGETARCH
|
||||
|
||||
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
|
||||
org.opencontainers.image.created="2026-03-06T15:06:30Z" \
|
||||
org.opencontainers.image.created="2026-04-05T15:33:48Z" \
|
||||
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
|
||||
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/minio/README.md" \
|
||||
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/minio" \
|
||||
@@ -50,7 +50,7 @@ RUN /opt/bitnami/scripts/minio-client/postunpack.sh
|
||||
RUN /opt/bitnami/scripts/minio/postunpack.sh
|
||||
ENV APP_VERSION="2025.10.15" \
|
||||
BITNAMI_APP_NAME="minio" \
|
||||
IMAGE_REVISION="10" \
|
||||
IMAGE_REVISION="11" \
|
||||
PATH="/opt/bitnami/minio-client/bin:/opt/bitnami/minio/bin:$PATH"
|
||||
|
||||
VOLUME [ "/bitnami/minio/data", "/certs" ]
|
||||
|
||||
+2
-20
@@ -42,25 +42,7 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
|
||||
|
||||
## Get this image
|
||||
|
||||
The recommended way to get the Bitnami MinIO(R) Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/minio).
|
||||
|
||||
```console
|
||||
docker pull bitnami/minio:latest
|
||||
```
|
||||
|
||||
To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/minio/tags/) in the Docker Hub Registry.
|
||||
|
||||
```console
|
||||
docker pull bitnami/minio:[TAG]
|
||||
```
|
||||
|
||||
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.
|
||||
|
||||
```console
|
||||
git clone https://github.com/bitnami/containers.git
|
||||
cd bitnami/APP/VERSION/OPERATING-SYSTEM
|
||||
docker build -t bitnami/APP:latest .
|
||||
```
|
||||
The Bitnami Bitnami Object Storage based on MinIO® Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
|
||||
|
||||
## Using `docker-compose.yaml`
|
||||
|
||||
@@ -167,7 +149,7 @@ Find more information about the Distributed Mode in the [MinIO(R) documentation]
|
||||
|
||||
### Reconfiguring Keys on container restarts
|
||||
|
||||
MinIO(R) configures the access & secret key during the 1st initialization based on the `MINIO_ROOT_USER` and `MINIO_ROOT_PASSWORD` environment variables, respetively.
|
||||
MinIO(R) configures the access & secret key during the 1st initialization based on the `MINIO_ROOT_USER` and `MINIO_ROOT_PASSWORD` environment variables, respectively.
|
||||
|
||||
When using persistence, MinIO(R) will reuse the data configured during the 1st initialization by default, ignoring whatever values are set on these environment variables. You can force MinIO(R) to reconfigure the keys based on the environment variables by setting the `MINIO_FORCE_NEW_KEYS` environment variable to `yes`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user