From 774d2eeae5218cbd4c4e6f36dadf782ecfb8210e Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 17 Feb 2023 16:34:47 +0100 Subject: [PATCH] [bitnami/mariadb] Release 10.10.3-debian-11-r3 (#24262) Signed-off-by: Bitnami Containers --- bitnami/mariadb/10.10/debian-11/Dockerfile | 14 +++++++------- .../opt/bitnami/.bitnami_components.json | 12 ++++++------ bitnami/mariadb/README.md | 8 ++++---- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/bitnami/mariadb/10.10/debian-11/Dockerfile b/bitnami/mariadb/10.10/debian-11/Dockerfile index e7e5c379f9cc..c34af505b2f9 100644 --- a/bitnami/mariadb/10.10/debian-11/Dockerfile +++ b/bitnami/mariadb/10.10/debian-11/Dockerfile @@ -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-17T15:09:09Z" \ + org.opencontainers.image.description="Application packaged by VMware, Inc" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="10.10.3-debian-11-r2" \ - org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/mariadb" \ + org.opencontainers.image.ref.name="10.10.3-debian-11-r3" \ org.opencontainers.image.title="mariadb" \ org.opencontainers.image.vendor="VMware, Inc." \ org.opencontainers.image.version="10.10.3" @@ -22,9 +22,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"] RUN install_packages ca-certificates curl libaio1 libaudit1 libcap-ng0 libcrypt1 libgcc-s1 libicu67 liblzma5 libncurses6 libpam0g libssl1.1 libstdc++6 libtinfo6 libxml2 procps psmisc zlib1g RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \ COMPONENTS=( \ - "ini-file-1.4.5-0-linux-${OS_ARCH}-debian-11" \ - "mariadb-10.10.3-0-linux-${OS_ARCH}-debian-11" \ - "gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \ + "ini-file-1.4.5-1-linux-${OS_ARCH}-debian-11" \ + "mariadb-10.10.3-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 \ diff --git a/bitnami/mariadb/10.10/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/mariadb/10.10/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json index 4c890fb74d7a..07b9a72ef9dd 100644 --- a/bitnami/mariadb/10.10/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json +++ b/bitnami/mariadb/10.10/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json @@ -1,23 +1,23 @@ { "gosu": { "arch": "amd64", - "digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b", + "digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa", "distro": "debian-11", "type": "NAMI", - "version": "1.16.0-1" + "version": "1.16.0-2" }, "ini-file": { "arch": "amd64", - "digest": "d82fb302437effeec0d20f104b35304c46cf295bb3af56ab00d69ad4ffd39eb0", + "digest": "75d5f74f62ca3a476e5ffc01715b197ba18c3b45a85b18fb61cc68e998616119", "distro": "debian-11", "type": "NAMI", - "version": "1.4.5-0" + "version": "1.4.5-1" }, "mariadb": { "arch": "amd64", - "digest": "fb66a3a0413e52526992f391ae4404b0caf47d8bf46c5235d5bc025f8db20550", + "digest": "6a84eb41eb4ba9baebd84d6d1f75970fa4dbd2ccb91e30456b1c671429af71e6", "distro": "debian-11", "type": "NAMI", - "version": "10.10.3-0" + "version": "10.10.3-1" } } \ No newline at end of file diff --git a/bitnami/mariadb/README.md b/bitnami/mariadb/README.md index c52d622dc6c2..56e5a414f6a9 100644 --- a/bitnami/mariadb/README.md +++ b/bitnami/mariadb/README.md @@ -137,7 +137,7 @@ docker run -it --rm \ bitnami/mariadb:latest mysql -h mariadb-server -u root ``` -### 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 MariaDB server from your own custom application image which is identified in the following snippet by the service name `myapp`. @@ -667,12 +667,12 @@ docker-compose up mariadb * Backwards compatibility is not guaranteed when data is persisted using docker-compose. You can use the workaround below to overcome it: ```console -docker-compose down +$ docker-compose down ## Change the mount point sed -i -e 's#mariadb_data:/bitnami#mariadb_data:/bitnami/mariadb#g' docker-compose.yml ## Pull the latest bitnami/mariadb image -docker pull bitnami/mariadb:latest -docker-compose up -d +$ docker pull bitnami/mariadb:latest +$ docker-compose up -d ``` ### 10.1.28-r2 and 10.2.16-r2