From 78cf68f4a33f53c368ab9df6c213b81ac385acc3 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 17 Feb 2023 17:23:19 +0100 Subject: [PATCH] [bitnami/mysql] Release 5.7.41-debian-11-r8 (#24285) Signed-off-by: Bitnami Containers --- bitnami/mysql/5.7/debian-11/Dockerfile | 14 +++++++------- .../opt/bitnami/.bitnami_components.json | 12 ++++++------ bitnami/mysql/README.md | 8 ++++---- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/bitnami/mysql/5.7/debian-11/Dockerfile b/bitnami/mysql/5.7/debian-11/Dockerfile index 73331dd392a4..4f2b780ba769 100644 --- a/bitnami/mysql/5.7/debian-11/Dockerfile +++ b/bitnami/mysql/5.7/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-17T16:02:04Z" \ + org.opencontainers.image.description="Application packaged by VMware, Inc" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="5.7.41-debian-11-r7" \ - org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/mysql" \ + org.opencontainers.image.ref.name="5.7.41-debian-11-r8" \ org.opencontainers.image.title="mysql" \ org.opencontainers.image.vendor="VMware, Inc." \ org.opencontainers.image.version="5.7.41" @@ -22,9 +22,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"] RUN install_packages ca-certificates curl libaio1 libcom-err2 libcrypt1 libgcc-s1 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libsasl2-2 libssl1.1 libstdc++6 libtinfo6 libtirpc3 procps psmisc RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \ COMPONENTS=( \ - "ini-file-1.4.5-0-linux-${OS_ARCH}-debian-11" \ - "mysql-5.7.41-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" \ + "mysql-5.7.41-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/mysql/5.7/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/mysql/5.7/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json index 3c948d9f50f0..16fe51e71587 100644 --- a/bitnami/mysql/5.7/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json +++ b/bitnami/mysql/5.7/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" }, "mysql": { "arch": "amd64", - "digest": "44cb99e313fd54db3bf05b54bd632c259a804caa0df15347919c6843a3e189d6", + "digest": "1e466550c161275ae65f386b6ae4fbd8778edb877f50b892e6a263763659e05e", "distro": "debian-11", "type": "NAMI", - "version": "5.7.41-0" + "version": "5.7.41-1" } } \ No newline at end of file diff --git a/bitnami/mysql/README.md b/bitnami/mysql/README.md index 594456240845..20ad63ec2f51 100644 --- a/bitnami/mysql/README.md +++ b/bitnami/mysql/README.md @@ -137,7 +137,7 @@ docker run -it --rm \ bitnami/mysql:latest mysql -h mysql-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 MySQL server from your own custom application image which is identified in the following snippet by the service name `myapp`. @@ -610,12 +610,12 @@ docker-compose up mysql * 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#mysql_data:/bitnami#mysql_data:/bitnami/mysql/data#g' docker-compose.yml ## Pull the latest bitnami/mysql image -docker pull bitnami/mysql:latest -docker-compose up -d +$ docker pull bitnami/mysql:latest +$ docker-compose up -d ``` ### 5.7.22-r18 and 8.0.11-r16