Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-04-06 01:07:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/mariadb] Release 10.5.18-debian-11-r5 (#14725)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2022-11-24 08:10:14 +01:00
committed by GitHub
parent 2aeb6b7400
commit b01707002e
3 changed files with 11 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/mariadb/10.5/debian-11/Dockerfile
View File

@@ -4,7 +4,7 @@ ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
org.opencontainers.image.ref.name="10.5.18-debian-11-r4" \
org.opencontainers.image.ref.name="10.5.18-debian-11-r5" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/mariadb" \
org.opencontainers.image.title="mariadb" \
org.opencontainers.image.vendor="VMware, Inc." \
@@ -21,9 +21,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.4-0-linux-${OS_ARCH}-debian-11" \
"mariadb-10.5.18-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.14.0-155-linux-${OS_ARCH}-debian-11" \
"ini-file-1.4.4-1-linux-${OS_ARCH}-debian-11" \
"mariadb-10.5.18-2-linux-${OS_ARCH}-debian-11" \
"gosu-1.14.0-156-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

12
bitnami/mariadb/10.5/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -1,23 +1,23 @@
{
"gosu": {
"arch": "amd64",
"digest": "f21869b27c26b9c3053bce8b419a0fdf1dc45fcf13a7c2058e0afb6996d3687f",
"digest": "7969f4cc8ad0a260f891cccf5694686a513f4706b48771d605645be1f3f072e2",
"distro": "debian-11",
"type": "NAMI",
"version": "1.14.0-155"
"version": "1.14.0-156"
},
"ini-file": {
"arch": "amd64",
"digest": "bf97f0becbc1f7af6e84b187909e6f6d16a924fbe88456f7f72f9c59e1616b9b",
"digest": "9b5793ab94c63d6384a29c88c06b3e33cf718112edc8358ac54ada72072c3f3e",
"distro": "debian-11",
"type": "NAMI",
"version": "1.4.4-0"
"version": "1.4.4-1"
},
"mariadb": {
"arch": "amd64",
"digest": "a0637dcc8a8b8c91adab519fce412c0a4126800e141aef8f6ee49bb311d86672",
"digest": "4ab963652072bd1fff46a41812f3f1171e98b2d5538d0ab2b74f7d3d7bf16953",
"distro": "debian-11",
"type": "NAMI",
"version": "10.5.18-0"
"version": "10.5.18-2"
}
}

5
bitnami/mariadb/README.md
View File

@@ -176,10 +176,7 @@ $ docker-compose up -d
### Initializing a new instance
The container can execute custom files on the first start and on every start. Files with extensions `.sh`, `.sql` and `.sql.gz` are supported.
- Files in `/docker-entrypoint-initdb.d` will only execute on the first container start.
- Files in `/docker-entrypoint-startdb.d` will execute on every container start.
When the container is executed for the first time, it will execute the files with extensions `.sh`, `.sql` and `.sql.gz` located at `/docker-entrypoint-startdb.d`.
In order to have your custom files inside the docker image you can mount them as a volume.