mirror of
https://github.com/bitnami/containers.git
synced 2026-02-14 16:47:21 +08:00
[bitnami/minio] Release 2023.2.10-debian-11-r2 (#24395)
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
@@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
|
||||
|
||||
ARG TARGETARCH
|
||||
|
||||
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
|
||||
org.opencontainers.image.description="Application packaged by Bitnami" \
|
||||
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
|
||||
org.opencontainers.image.created="2023-02-17T18:07:14Z" \
|
||||
org.opencontainers.image.description="Application packaged by VMware, Inc" \
|
||||
org.opencontainers.image.licenses="Apache-2.0" \
|
||||
org.opencontainers.image.ref.name="2023.2.10-debian-11-r1" \
|
||||
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/minio" \
|
||||
org.opencontainers.image.ref.name="2023.2.10-debian-11-r2" \
|
||||
org.opencontainers.image.title="minio" \
|
||||
org.opencontainers.image.vendor="VMware, Inc." \
|
||||
org.opencontainers.image.version="2023.2.10"
|
||||
@@ -22,10 +22,10 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
|
||||
RUN install_packages ca-certificates curl jq procps
|
||||
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
|
||||
COMPONENTS=( \
|
||||
"wait-for-port-1.0.6-0-linux-${OS_ARCH}-debian-11" \
|
||||
"minio-client-2023.1.28-0-linux-${OS_ARCH}-debian-11" \
|
||||
"minio-2023.2.10-0-linux-${OS_ARCH}-debian-11" \
|
||||
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
|
||||
"wait-for-port-1.0.6-1-linux-${OS_ARCH}-debian-11" \
|
||||
"minio-client-2023.1.28-1-linux-${OS_ARCH}-debian-11" \
|
||||
"minio-2023.2.10-1-linux-${OS_ARCH}-debian-11" \
|
||||
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
|
||||
) && \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
|
||||
|
||||
@@ -1,30 +1,30 @@
|
||||
{
|
||||
"gosu": {
|
||||
"arch": "amd64",
|
||||
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
|
||||
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "1.16.0-1"
|
||||
"version": "1.16.0-2"
|
||||
},
|
||||
"minio": {
|
||||
"arch": "amd64",
|
||||
"digest": "5491ed91b92fe411ae179823562af080ceec00409185db0e0f024b1fa106e104",
|
||||
"digest": "525202a593d8c04a54297bf77651805fcfc1989f3529f5398e3ef9369456a8b3",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "2023.2.10-0"
|
||||
"version": "2023.2.10-1"
|
||||
},
|
||||
"minio-client": {
|
||||
"arch": "amd64",
|
||||
"digest": "6f76d77ad3e11b2eb53bc153076fb82f9cc2f65f32217427144d0fbe7aed7eb0",
|
||||
"digest": "97bf857c0cf73069964e49fdb6583f1b771a55249703909cabe4ee0c59433a2e",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "2023.1.28-0"
|
||||
"version": "2023.1.28-1"
|
||||
},
|
||||
"wait-for-port": {
|
||||
"arch": "amd64",
|
||||
"digest": "f9199cd66b92fef328ecfbc5ffbc8f14be33257a4e34b8c6ba35a730c5a2f59d",
|
||||
"digest": "be7c393d598ddf16d1c3c008a67b87879e48aca62071a208583390f2b41e6744",
|
||||
"distro": "debian-11",
|
||||
"type": "NAMI",
|
||||
"version": "1.0.6-0"
|
||||
"version": "1.0.6-1"
|
||||
}
|
||||
}
|
||||
@@ -139,7 +139,7 @@ docker run -it --rm --name minio-client \
|
||||
mb minio/my-bucket
|
||||
```
|
||||
|
||||
### Using Docker Compose
|
||||
### Using a Docker Compose file
|
||||
|
||||
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the MinIO(R) server from your own custom application image which is identified in the following snippet by the service name `myapp`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user