diff --git a/bitnami/flink/1/debian-12/Dockerfile b/bitnami/flink/1/debian-12/Dockerfile index 989d1f2a89c6..2240afa78521 100644 --- a/bitnami/flink/1/debian-12/Dockerfile +++ b/bitnami/flink/1/debian-12/Dockerfile @@ -9,11 +9,11 @@ ARG TARGETARCH LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2024-11-09T21:12:53Z" \ + org.opencontainers.image.created="2024-12-09T21:46:18Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/flink/README.md" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="1.20.0-debian-12-r8" \ + org.opencontainers.image.ref.name="1.20.0-debian-12-r9" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/flink" \ org.opencontainers.image.title="flink" \ org.opencontainers.image.vendor="Broadcom, Inc." \ diff --git a/bitnami/flink/1/debian-12/rootfs/opt/bitnami/scripts/java/entrypoint.sh b/bitnami/flink/1/debian-12/rootfs/opt/bitnami/scripts/java/entrypoint.sh index 8557631d2549..38802fc0bfe9 100755 --- a/bitnami/flink/1/debian-12/rootfs/opt/bitnami/scripts/java/entrypoint.sh +++ b/bitnami/flink/1/debian-12/rootfs/opt/bitnami/scripts/java/entrypoint.sh @@ -13,6 +13,11 @@ set -o pipefail . /opt/bitnami/scripts/libbitnami.sh . /opt/bitnami/scripts/liblog.sh +if [[ "$OS_FLAVOUR" =~ photon && "$APP_VERSION" =~ ^1.8 ]]; then + # Option --module-path is not supported by JAVA 1.8 since modules were added in version 1.9 + unset JAVA_TOOL_OPTIONS +fi + print_welcome_page echo "" diff --git a/bitnami/flink/README.md b/bitnami/flink/README.md index b635119a62dd..d8b1f47bf8aa 100644 --- a/bitnami/flink/README.md +++ b/bitnami/flink/README.md @@ -27,7 +27,7 @@ Looking to use Apache Flink in production? Try [VMware Tanzu Application Catalog ## 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://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html). +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). You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`. @@ -57,7 +57,7 @@ docker build -t bitnami/APP:latest . ## 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://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-work-with-non-root-containers-index.html). +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). ## Configuration