[bitnami/java] Release 25.0.1-13-debian-12-r0 (#88483)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2025-11-20 20:04:18 +01:00
committed by GitHub
parent af65209bc5
commit 1fd73a504d
2 changed files with 36 additions and 4 deletions

View File

@@ -8,13 +8,13 @@ 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="2025-10-29T14:31:12Z" \
org.opencontainers.image.created="2025-11-20T18:51:26Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/java/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/java" \
org.opencontainers.image.title="java" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="25.0.1-11"
org.opencontainers.image.version="25.0.1-13"
ENV OS_ARCH="${TARGETARCH:-amd64}" \
OS_FLAVOUR="debian-12" \
@@ -28,7 +28,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=( \
"java-25.0.1-11-0-linux-${OS_ARCH}-debian-12" \
"java-25.0.1-13-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -52,7 +52,7 @@ RUN sed -i 's/^PASS_MAX_DAYS.*/PASS_MAX_DAYS 90/' /etc/login.defs && \
COPY rootfs /
RUN /opt/bitnami/scripts/java/postunpack.sh
ENV APP_VERSION="25.0.1-11" \
ENV APP_VERSION="25.0.1-13" \
BITNAMI_APP_NAME="java" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \

View File

@@ -36,6 +36,38 @@ 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).
## Choosing between the _Standard_ and _Minimal_ image
This asset is available in two flavors: _Standard_ and _Minimal_; designed to address different use cases and operational needs.
### Standard images
The standard images are full-featured, production-ready containers built on top of secure base operating systems. They include:
- The complete runtime and commonly used system tools.
- A familiar Linux environment (shell, package manager, debugging utilities).
- Full compatibility with most CI/CD pipelines and existing workloads.
Recommended for:
- Development and testing environments.
- Workloads requiring package installation or debugging tools.
- Applications that depend on system utilities or shared libraries.
### Minimal images
The minimal images are optimized, distroless-style containers derived from a stripped-down base. They only ship whats strictly necessary to run the application; no shell, package manager, or extra libraries. They provide:
- Smaller size: Faster pull and startup times.
- Reduced attack surface: Fewer components and potential vulnerabilities.
- Simpler maintenance: Fewer dependencies to patch or update.
Recommended for:
- Production environments prioritizing performance and security.
- Regulated or security-sensitive workloads
- Containers built via multi-stage builds (e.g., Golang static binaries).
## 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).