[bitnami/ray] Release 2.54.1-debian-12-r0 (#91842)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>

bitnami/ray/2/debian-12/Dockerfile

@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
 ARG TARGETARCH
 
 LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
-      org.opencontainers.image.created="2026-03-02T20:54:55Z" \
+      org.opencontainers.image.created="2026-03-26T04:39:04Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/ray/README.md" \
       org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/ray" \
       org.opencontainers.image.title="ray" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
-      org.opencontainers.image.version="2.54.0"
+      org.opencontainers.image.version="2.54.1"
 
 ENV HOME="/" \
     OS_ARCH="${TARGETARCH:-amd64}" \
@@ -28,8 +28,8 @@ 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=( \
-      "python-3.12.12-23-linux-${OS_ARCH}-debian-12" \
-      "ray-2.54.0-1-linux-${OS_ARCH}-debian-12" \
+      "python-3.12.13-2-linux-${OS_ARCH}-debian-12" \
+      "ray-2.54.1-0-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -48,9 +48,9 @@ RUN mkdir /.local && chmod g+rwX /.local
 RUN uninstall_packages curl
 
 RUN mkdir /app && chmod g+rwX /app && ln -s /opt/bitnami/python/bin/ray /usr/bin/ray && ln -s /opt/bitnami/python/bin/python /usr/bin/python
-ENV APP_VERSION="2.54.0" \
+ENV APP_VERSION="2.54.1" \
     BITNAMI_APP_NAME="ray" \
-    IMAGE_REVISION="1" \
+    IMAGE_REVISION="0" \
     PATH="/opt/bitnami/python/bin:$PATH"
 
 WORKDIR /app

bitnami/ray/README.md

@@ -5,7 +5,7 @@
 [Overview of Ray](https://ray.io)
 Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
 
-## <a id="tl-dr"></a> TL;DR
+## TL;DR
 
 Use this quick command to run the container.
 
@@ -13,7 +13,7 @@ Use this quick command to run the container.
 docker run -it --name ray bitnami/ray
 ```
 
-## <a id="why-use-bitnami-secure-images"></a> Why use Bitnami Secure Images?
+## Why use Bitnami Secure Images?
 
 Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
 
@@ -30,15 +30,15 @@ Each image comes with valuable security metadata. You can view the metadata in [
 
 If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
 
-## <a id="why-non-root"></a> Why use a non-root container?
+## Why use a non-root container?
 
 Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
 
-## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
+## Supported tags and respective `Dockerfile` links
 
 Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
 
-## <a id="get-this-image"></a> Get this image
+## Get this image
 
 The recommended way to get the Bitnami Ray Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/ray).
 
@@ -60,7 +60,7 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
 docker build -t bitnami/APP:latest .
 ```
 
-## <a id="entering-the-repl"></a> Entering the REPL
+## Entering the REPL
 
 By default, running this image will drop you into the Python REPL, where you can interactively test and try things out with Ray in Python.
 
@@ -68,11 +68,11 @@ By default, running this image will drop you into the Python REPL, where you can
 docker run -it --name ray bitnami/ray
 ```
 
-## <a id="configuration"></a> Configuration
+## Configuration
 
 The following sections describe how to run your app and configure FIPS.
 
-### <a id="running-your-ray-app"></a> Running your Ray app
+### Running your Ray app
 
 The default work directory for the Ray image is `/app`. You can mount a folder from your host here that includes your Ray script and run it normally using the `python` command.
 
@@ -81,7 +81,7 @@ docker run -it --name ray -v /path/to/app:/app bitnami/ray \
   python script.py
 ```
 
-### <a id="running-ray-app-with-dependencies"></a> Running a Ray app with package dependencies
+### Running a Ray app with package dependencies
 
 If your Ray app has a `requirements.txt` defining your app's dependencies, you can install the dependencies before running your app.
 
@@ -94,13 +94,13 @@ docker run -it --name ray -v /path/to/app:/app bitnami/ray \
 
 - [Ray documentation](https://ray.iodocs/)
 
-### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
+### FIPS configuration in Bitnami Secure Images
 
 The Bitnami Ray Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
 
 - `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
 
-## <a id="notable-changes"></a> Notable changes
+## Notable changes
 
 The following subsections describe notable changes.
 
@@ -108,7 +108,7 @@ The following subsections describe notable changes.
 
 - The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
 
-## <a id="license"></a> License
+## License
 
 Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.