[bitnami/tensorflow-resnet] Release 2.14.1-debian-11-r6 (#55196)

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

bitnami/tensorflow-resnet/2/debian-11/Dockerfile

@@ -7,10 +7,10 @@ ARG TARGETARCH
 
 LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
       org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
-      org.opencontainers.image.created="2023-12-26T14:01:04Z" \
+      org.opencontainers.image.created="2024-01-20T05:18:20Z" \
       org.opencontainers.image.description="Application packaged by VMware, Inc" \
       org.opencontainers.image.licenses="Apache-2.0" \
-      org.opencontainers.image.ref.name="2.14.1-debian-11-r5" \
+      org.opencontainers.image.ref.name="2.14.1-debian-11-r6" \
       org.opencontainers.image.title="tensorflow-resnet" \
       org.opencontainers.image.vendor="VMware, Inc." \
       org.opencontainers.image.version="2.14.1"
@@ -40,6 +40,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
 RUN apt-get update && apt-get upgrade -y && \
     apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
 RUN chmod g+rwX /opt/bitnami
+RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
 RUN mkdir /.local && chmod g+rwX /.local
 
 COPY rootfs /

bitnami/tensorflow-resnet/2/debian-11/docker-compose.yml

@@ -1,25 +0,0 @@
-# Copyright VMware, Inc.
-# SPDX-License-Identifier: APACHE-2.0
-
-version: "2"
-services:
-  tensorflow-serving:
-    image: docker.io/bitnami/tensorflow-serving:2
-    ports:
-      - 8500:8500
-      - 8501:8501
-    volumes:
-      - "tensorflow_serving_data:/bitnami"
-      - "/tmp/model-data:/bitnami/model-data"
-  tensorflow-resnet:
-    image: docker.io/bitnami/tensorflow-resnet:2
-    depends_on:
-      - tensorflow-serving
-    volumes:
-      - "tensorflow_resnet_data:/bitnami"
-      - "/tmp/model-data:/bitnami/model-data"
-volumes:
-  tensorflow_serving_data:
-    driver: local
-  tensorflow_resnet_data:
-    driver: local

bitnami/tensorflow-resnet/2/debian-11/prebuildfs/usr/sbin/run-script

@@ -10,7 +10,7 @@ fi
 
 script=$1
 exit_code="${2:-96}"
-fail_if_not_present="${3:-y}"
+fail_if_not_present="${3:-n}"
 
 if test -f "$script"; then
   sh $script

bitnami/tensorflow-resnet/README.md

@@ -18,13 +18,6 @@ curl -o resnet_50_classification_1.tar.gz https://storage.googleapis.com/tfhub-m
 tar xzf resnet_50_classification_1.tar.gz -C 1
 ```
 
-### Docker Compose
-
-```console
-curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/tensorflow-resnet/docker-compose.yml > docker-compose.yml
-docker-compose up -d
-```
-
 ## Why use Bitnami Images?
 
 * Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
@@ -50,27 +43,16 @@ Subscribe to project updates by watching the [bitnami/containers GitHub repo](ht
 
 ## Prerequisites
 
-To run this application you need Docker Engine 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.
+To run this application you need Docker Engine 1.10.0.
 
 ## How to use this image
 
 ### Run TensorFlow ResNet client with TensorFlow Serving
 
-Running TensorFlow ResNet client with the TensorFlow Serving server is the recommended way. You can either use docker-compose or run the containers manually.
-
-#### Run the application using Docker Compose
-
-The main folder of this repository contains a functional [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/tensorflow-resnet/docker-compose.yml) file. Run the application using it as shown below:
-
-```console
-curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/tensorflow-resnet/docker-compose.yml > docker-compose.yml
-docker-compose up -d
-```
+Running TensorFlow ResNet client with the TensorFlow Serving server is the recommended way.
 
 #### Run the application manually
 
-If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
-
 1. Create a new network for the application and the database:
 
     ```console
@@ -103,8 +85,7 @@ Bitnami provides up-to-date versions of Tensorflow-Serving and TensorFlow ResNet
 
 2. Stop your container
 
-    * For docker-compose: `$ docker-compose stop tensorflow-resnet`
-    * For manual execution: `$ docker stop tensorflow-resnet`
+    * `$ docker stop tensorflow-resnet`
 
 3. Take a snapshot of the application state
 
@@ -118,13 +99,11 @@ You can use these snapshots to restore the application state should the upgrade
 
 1. Remove the currently running container
 
-    * For docker-compose: `$ docker-compose rm tensorflow-resnet`
-    * For manual execution: `$ docker rm tensorflow-resnet`
+    * `$ docker rm tensorflow-resnet`
 
 2. Run the new image
 
-    * For docker-compose: `$ docker-compose up tensorflow-resnet`
-    * For manual execution (mount the directories if needed): `docker run --name tensorflow-resnet bitnami/tensorflow-resnet:latest`
+    * Mount the directories if needed: `docker run --name tensorflow-resnet bitnami/tensorflow-resnet:latest`
 
 ## Configuration
 
@@ -162,11 +141,21 @@ Once you have deployed both the TensorFlow Serving and TensorFlow ResNet contain
 
 Tensorflow Resnet can be customized by specifying environment variables on the first run. The following environment values are provided to custom Tensorflow:
 
-* `TF_RESNET_SERVING_PORT_NUMBER`: TensorFlow Serving Port. Default: **8500**
-* `TF_RESNET_SERVING_HOST`: TensorFlow Serving server name. Default: **tensorflow-serving**
+#### Customizable environment variables
+
+| Name                            | Description                    | Default Value        |
+|---------------------------------|--------------------------------|----------------------|
+| `TF_RESNET_SERVING_PORT_NUMBER` | Tensorflow serving port number | `8500`               |
+| `TF_RESNET_SERVING_HOST`        | Tensorflow serving host name   | `tensorflow-serving` |
+
+#### Read-only environment variables
 
 ## Notable Changes
 
+### Starting January 16, 2024
+
+* The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
+
 ### 2.4.1-debian-10-r87
 
 * The container initialization logic is now using bash.