[bitnami/mariadb] Release 10.8.3-debian-11-r11 (#768)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2022-07-26 08:58:20 +00:00
committed by GitHub
parent e473d4dc47
commit adc180bccc
3 changed files with 6 additions and 4 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
# Install required system packages and dependencies
RUN install_packages acl ca-certificates curl gzip libaio1 libaudit1 libc6 libcap-ng0 libcrypt1 libgcc-s1 libicu67 liblzma5 libncurses6 libpam0g libssl1.1 libstdc++6 libtinfo6 libxml2 procps psmisc tar zlib1g
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "ini-file" "1.4.3-151" --checksum 3f23f4fff5bd0ebead5b1a59c450e7b9806198864ff9c765439df14bfb9e1cf4
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "mariadb" "10.8.3-151" --checksum 91a79f8d13b99b49f6e54203a06cd96728b84e92e7d81460259fe0d7fcffd2c1
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "mariadb" "10.8.3-152" --checksum 9db40c25695569d414569bae3e2f13d5c6f3288aff59f8744e302358c35f945f
RUN . /opt/bitnami/scripts/libcomponent.sh && component_unpack "gosu" "1.14.0-152" --checksum 0c751c7e2ec0bc900a19dbec0306d6294fe744ddfb0fa64197ba1a36040092f0
RUN apt-get update && apt-get upgrade -y && \
rm -r /var/lib/apt/lists /var/cache/apt/archives
@@ -15,9 +15,9 @@
},
"mariadb": {
"arch": "amd64",
"digest": "91a79f8d13b99b49f6e54203a06cd96728b84e92e7d81460259fe0d7fcffd2c1",
"digest": "9db40c25695569d414569bae3e2f13d5c6f3288aff59f8744e302358c35f945f",
"distro": "debian-11",
"type": "NAMI",
"version": "10.8.3-151"
"version": "10.8.3-152"
}
}
+3 -1
View File
@@ -47,7 +47,7 @@ Non-root container images add an extra layer of security and are generally recom
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`10.8`, `10.8-debian-11`, `10.8.3`, `10.8.3-debian-11-r10`, `latest` (10.8/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-mariadb/blob/10.8.3-debian-11-r10/10.8/debian-11/Dockerfile)
* [`10.8`, `10.8-debian-11`, `10.8.3`, `10.8.3-debian-11-r11`, `latest` (10.8/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-mariadb/blob/10.8.3-debian-11-r11/10.8/debian-11/Dockerfile)
* [`10.8`, `10.8-debian-10`, `10.8.3`, `10.8.3-debian-10-r-1`, `latest` (10.8/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-mariadb/blob/10.8.3-debian-10-r-1/10.8/debian-10/Dockerfile)
* [`10.7`, `10.7-debian-11`, `10.7.4`, `10.7.4-debian-11-r19` (10.7/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-mariadb/blob/10.7.4-debian-11-r19/10.7/debian-11/Dockerfile)
* [`10.6`, `10.6-debian-11`, `10.6.8`, `10.6.8-debian-11-r18` (10.6/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-mariadb/blob/10.6.8-debian-11-r18/10.6/debian-11/Dockerfile)
@@ -582,6 +582,8 @@ or using Docker Compose:
$ docker-compose logs mariadb
```
To increase the verbosity on intialization or add extra debug information, you can assign the `BITNAMI_DEBUG` environment variable to `true`.
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance