From 44425c36746f9361a6cf5521548dc3f15afd9f57 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 5 Mar 2026 09:33:25 +0100 Subject: [PATCH] [bitnami/chainloop-control-plane-migrations] Release 1.80.0-debian-12-r0 (#91239) Signed-off-by: Bitnami Bot --- .../1/debian-12/Dockerfile | 8 ++++---- .../chainloop-control-plane-migrations/README.md | 16 ++++++++-------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/bitnami/chainloop-control-plane-migrations/1/debian-12/Dockerfile b/bitnami/chainloop-control-plane-migrations/1/debian-12/Dockerfile index 805913808057..19dc217ba4b8 100644 --- a/bitnami/chainloop-control-plane-migrations/1/debian-12/Dockerfile +++ b/bitnami/chainloop-control-plane-migrations/1/debian-12/Dockerfile @@ -18,7 +18,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ "atlas-1.1.0-2-linux-${OS_ARCH}-debian-12" \ - "chainloop-control-plane-migrations-1.79.1-0-linux-${OS_ARCH}-debian-12" \ + "chainloop-control-plane-migrations-1.80.0-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -41,11 +41,11 @@ ARG TARGETARCH ENV OS_ARCH="${TARGETARCH:-amd64}" LABEL org.opencontainers.image.base.name="scratch" \ - org.opencontainers.image.created="2026-03-02T16:54:41Z" \ + org.opencontainers.image.created="2026-03-05T08:21:12Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.title="chainloop-control-plane-migrations" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="1.79.1" + org.opencontainers.image.version="1.80.0" COPY rootfs / COPY --from=builder /opt/bitnami/chainloop/migrations /migrations @@ -55,7 +55,7 @@ COPY --from=builder /opt/bitnami/atlas/licenses /opt/bitnami/atlas/licenses COPY --from=builder /opt/bitnami/chainloop/.spdx-chainloop-control-plane-migrations.spdx /opt/bitnami/chainloop/.spdx-chainloop-control-plane-migrations.spdx COPY --from=builder /opt/bitnami/chainloop/licenses /opt/bitnami/chainloop/licenses -ENV APP_VERSION="1.79.1" \ +ENV APP_VERSION="1.80.0" \ BITNAMI_APP_NAME="chainloop-control-plane-migrations" \ IMAGE_REVISION="0" \ PATH="/opt/bitnami/atlas/bin:$PATH" diff --git a/bitnami/chainloop-control-plane-migrations/README.md b/bitnami/chainloop-control-plane-migrations/README.md index 640d7a5eb066..732a43916b3c 100644 --- a/bitnami/chainloop-control-plane-migrations/README.md +++ b/bitnami/chainloop-control-plane-migrations/README.md @@ -5,13 +5,13 @@ [Overview of Chainloop Control Plane migrations](https://chainloop.dev) 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. -## TL;DR +## TL;DR ```console docker run --name chainloop-control-plane-migrations bitnami/chainloop-control-plane-migrations:latest ``` -## 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? @@ -28,15 +28,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). -## 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). -## 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). -## Get this image +## Get this image The recommended way to get the Bitnami Chainloop Control Plane migrations Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/chainloop-control-plane-migrations). @@ -58,11 +58,11 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` -## Configuration +## Configuration The following section describes how to run commands -### Running commands +### Running commands To run commands inside this container you can use `docker run`, for example to execute `chainloop-control-plane-migrations help` you can follow the example below: @@ -72,7 +72,7 @@ docker run --rm --name chainloop-control-plane-migrations bitnami/chainloop-cont Check the [official Chainloop Control Plane migrations documentation](https://github.com/chainloop-dev/chainloop/tree/main/app/controlplane) for more information about configuration options. -## License +## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.