[bitnami/tensorflow-serving] Release 2.19.1-debian-12-r14 (#93011)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-05-09 00:25:41 +02:00 committed by GitHub
parent d4c07c78f9
commit f52a8d2d28
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 11 additions and 23 deletions

View File

@ -8,7 +8,7 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T21:47:46Z" \
org.opencontainers.image.created="2026-05-08T22:12:14Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/tensorflow-serving/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/tensorflow-serving" \
@ -30,7 +30,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-165-linux-${OS_ARCH}-debian-12" \
"tensorflow-serving-2.19.1-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@ -54,7 +54,7 @@ RUN /opt/bitnami/scripts/java/postunpack.sh
RUN /opt/bitnami/scripts/tensorflow-serving/postunpack.sh
ENV APP_VERSION="2.19.1" \
BITNAMI_APP_NAME="tensorflow-serving" \
IMAGE_REVISION="13" \
IMAGE_REVISION="14" \
JAVA_HOME="/opt/bitnami/java"
EXPOSE 8500

View File

@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name tensorflow-serving bitnami/tensorflow-serving:latest
```
You can find the available configuration options in the [Environment Variables](#environment-variables) section.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/tensorflow-serving/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/tensorflow-serving/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/tensorflow-resnet).
## Why use Bitnami Secure Images?
@ -42,10 +48,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami TensorFlow Serving Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/tensorflow-resnet).
## Persisting your configuration
If you remove the container all your data and configurations will be lost, and the next time you run the image the data and configurations will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@ -109,21 +111,7 @@ The Bitnami TensorFlow Serving Docker image from the [Bitnami Secure Images](htt
## Logging
The Bitnami TensorFlow Serving Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs tensorflow-serving
```
or using Docker Compose:
```console
docker-compose logs tensorflow-serving
```
The logs are also stored inside the container in the /opt/bitnami/tensorflow-serving/logs/tensorflow-serving.log file.
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.
The Bitnami TensorFlow Serving Docker image sends the container logs to the `stdout`. 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.
## Notable Changes