Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-02-19 22:17:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/minio] Release 2023.9.16-debian-11-r2 (#49153)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-09-19 14:22:07 +02:00
committed by GitHub
parent 6dfd8b71cf
commit 1e1bf37f1c
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bitnami/minio/2023/debian-11/Dockerfile
View File

@@ -7,10 +7,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-09-16T11:14:30Z" \
org.opencontainers.image.created="2023-09-18T15:17:26Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2023.9.16-debian-11-r0" \
org.opencontainers.image.ref.name="2023.9.16-debian-11-r2" \
org.opencontainers.image.title="minio" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="2023.9.16"

20
bitnami/minio/README.md
View File

@@ -75,13 +75,13 @@ docker build -t bitnami/APP:latest .
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the `/data` path.
For persistence you should mount a directory at the `/bitnami/minio/data` path.
```console
docker run --name minio \
--publish 9000:9000 \
--publish 9001:9001 \
--volume /path/to/minio-persistence:/data \
--volume /path/to/minio-persistence:/bitnami/minio/data \
bitnami/minio:latest
```
@@ -92,7 +92,7 @@ services:
minio:
...
volumes:
- /path/to/minio-persistence:/data
- /path/to/minio-persistence:/bitnami/minio/data
...
```
@@ -312,23 +312,23 @@ services:
minio-0:
image: 'bitnami/minio:latest'
volumes:
- 'minio_0_data_0:/data-0'
- 'minio_0_data_1:/data-1'
- 'minio_0_data_0:/bitnami/minio/data-0'
- 'minio_0_data_1:/bitnami/minio/data-1'
environment:
- MINIO_ROOT_USER=minio
- MINIO_ROOT_PASSWORD=miniosecret
- MINIO_DISTRIBUTED_MODE_ENABLED=yes
- MINIO_DISTRIBUTED_NODES=minio-{0...1}/data-{0...1}
- MINIO_DISTRIBUTED_NODES=minio-{0...1}/bitnami/minio/data-{0...1}
minio-1:
image: 'bitnami/minio:latest'
volumes:
- 'minio_1_data_0:/data-0'
- 'minio_1_data_1:/data-1'
- 'minio_1_data_0:/bitnami/minio/data-0'
- 'minio_1_data_1:/bitnami/minio/data-1'
environment:
- MINIO_ROOT_USER=minio
- MINIO_ROOT_PASSWORD=miniosecret
- MINIO_DISTRIBUTED_MODE_ENABLED=yes
- MINIO_DISTRIBUTED_NODES=minio-{0...1}/data-{0...1}
- MINIO_DISTRIBUTED_NODES=minio-{0...1}/bitnami/minio/data-{0...1}
volumes:
minio_0_data_0:
driver: local
@@ -355,7 +355,7 @@ docker run --name minio \
--env MINIO_FORCE_NEW_KEYS="yes" \
--env MINIO_ROOT_USER="new-minio-root-user" \
--env MINIO_ROOT_PASSWORD="new-minio-root-password" \
--volume /path/to/minio-persistence:/data \
--volume /path/to/minio-persistence:/bitnami/minio/data \
bitnami/minio:latest
```