[bitnami/memcached] Release 1.6.18-debian-11-r14 (#24303)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 17:32:49 +01:00 committed by GitHub
parent b0fded0595
commit 3d870f8290
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 11 additions and 11 deletions

View File

@ -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:13:24Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.6.18-debian-11-r13" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/memcached" \
org.opencontainers.image.ref.name="1.6.18-debian-11-r14" \
org.opencontainers.image.title="memcached" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="1.6.18"
@ -22,8 +22,8 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libevent-2.1-7 libsasl2-2 libsasl2-modules procps sasl2-bin
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"memcached-1.6.18-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"memcached-1.6.18-2-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 \

View File

@ -1,16 +1,16 @@
{
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"memcached": {
"arch": "amd64",
"digest": "6209cd9a4f94a895179fdb2077e28882f4780d232fb98592c666b46519b4b7b1",
"digest": "054239ab91a6ea7d2ac024215b96b049d3191169c1adb0321aed9079c8704df6",
"distro": "debian-11",
"type": "NAMI",
"version": "1.6.18-1"
"version": "1.6.18-2"
}
}

View File

@ -107,7 +107,7 @@ docker run -d --name myapp \
> 1. Please update the **YOUR_APPLICATION_IMAGE_** placeholder in the above snippet with your application image
> 2. In your application container, use the hostname `memcached-server` to connect to the Memcached server
### 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 Memcached server from your own custom application image which is identified in the following snippet by the service name `myapp`.