Skip to content

Commit 95bd1ad

Browse files
bitnami-botbitnami-bot
authored
[bitnami/kes] Release kes-2025.3.12-debian-12-r0 (#79133)
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
1 parent b2d619c commit 95bd1ad

File tree

8 files changed

+4089
-0
lines changed

8 files changed

+4089
-0
lines changed

‎bitnami/kes/2025/debian-12/Dockerfile‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# Copyright Broadcom, Inc. All Rights Reserved.
2+
# SPDX-License-Identifier: APACHE-2.0
3+
4+
FROM docker.io/bitnami/minideb:bookworm AS builder
5+
6+
ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
7+
ARG TARGETARCH
8+
9+
ENV OS_ARCH="${TARGETARCH:-amd64}"
10+
11+
COPY prebuildfs /
12+
SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
13+
14+
# Install required system packages and dependencies
15+
RUN install_packages ca-certificates curl
16+
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
17+
COMPONENTS=( \
18+
"kes-2025.3.12-0-linux-${OS_ARCH}-debian-12" \
19+
) ; \
20+
for COMPONENT in "${COMPONENTS[@]}"; do \
21+
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
22+
curl -SsLf "https://${DOWNLOADS_URL}/${COMPONENT}.tar.gz" -O ; \
23+
curl -SsLf "https://${DOWNLOADS_URL}/${COMPONENT}.tar.gz.sha256" -O ; \
24+
fi ; \
25+
sha256sum -c "${COMPONENT}.tar.gz.sha256" ; \
26+
tar -zxf "${COMPONENT}.tar.gz" -C /opt/bitnami --strip-components=2 --no-same-owner ; \
27+
rm -rf "${COMPONENT}".tar.gz{,.sha256} ; \
28+
done
29+
30+
######
31+
32+
FROM scratch
33+
34+
ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
35+
ARG TARGETARCH
36+
37+
ENV OS_ARCH="${TARGETARCH:-amd64}"
38+
39+
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
40+
org.opencontainers.image.base.name="scratch" \
41+
org.opencontainers.image.created="2025-03-25T12:03:41Z" \
42+
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
43+
org.opencontainers.image.ref.name="2025.3.12-debian-12-r0" \
44+
org.opencontainers.image.title="kes" \
45+
org.opencontainers.image.vendor="Broadcom, Inc." \
46+
org.opencontainers.image.version="2025.3.12"
47+
48+
COPY rootfs /
49+
COPY --from=builder /opt/bitnami/kes/bin /
50+
COPY --from=builder /opt/bitnami/kes/.spdx-kes.spdx /opt/bitnami/kes/.spdx-kes.spdx
51+
COPY --from=builder /opt/bitnami/kes/licenses /opt/bitnami/kes/licenses
52+
53+
ENV APP_VERSION="2025.3.12" \
54+
BITNAMI_APP_NAME="kes" \
55+
PATH="/"
56+
57+
USER 1001
58+
59+
ENTRYPOINT [ "/kes" ]

‎bitnami/kes/2025/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"kes": {
3+
"arch": "amd64",
4+
"distro": "debian-12",
5+
"type": "NAMI",
6+
"version": "2025.3.12-0"
7+
}
8+
}

‎bitnami/kes/2025/debian-12/prebuildfs/opt/bitnami/licenses/licenses.txt‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
Bitnami containers ship with software bundles. You can find the licenses under:
2+
/opt/bitnami/[name-of-bundle]/licenses/[bundle-version].txt

‎bitnami/kes/2025/debian-12/prebuildfs/usr/sbin/install_packages‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
#!/bin/sh
2+
# Copyright Broadcom, Inc. All Rights Reserved.
3+
# SPDX-License-Identifier: APACHE-2.0
4+
set -eu
5+
6+
n=0
7+
max=2
8+
export DEBIAN_FRONTEND=noninteractive
9+
10+
until [ $n -gt $max ]; do
11+
set +e
12+
(
13+
apt-get update -qq &&
14+
apt-get install -y --no-install-recommends "$@"
15+
)
16+
CODE=$?
17+
set -e
18+
if [ $CODE -eq 0 ]; then
19+
break
20+
fi
21+
if [ $n -eq $max ]; then
22+
exit $CODE
23+
fi
24+
echo "apt failed, retrying"
25+
n=$(($n + 1))
26+
done
27+
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives

‎bitnami/kes/2025/debian-12/prebuildfs/usr/sbin/run-script‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
#!/bin/sh
2+
# Copyright Broadcom, Inc. All Rights Reserved.
3+
# SPDX-License-Identifier: APACHE-2.0
4+
set -u
5+
6+
if [ $# -eq 0 ]; then
7+
>&2 echo "No arguments provided"
8+
exit 1
9+
fi
10+
11+
script=$1
12+
exit_code="${2:-96}"
13+
fail_if_not_present="${3:-n}"
14+
15+
if test -f "$script"; then
16+
sh $script
17+
18+
if [ $? -ne 0 ]; then
19+
exit $((exit_code))
20+
fi
21+
elif [ "$fail_if_not_present" = "y" ]; then
22+
>&2 echo "script not found: $script"
23+
exit 127
24+
fi

‎bitnami/kes/2025/debian-12/rootfs/etc/ssl/certs/ca-certificates.crt‎

Lines changed: 3864 additions & 0 deletions
Large diffs are not rendered by default.

‎bitnami/kes/2025/debian-12/tags-info.yaml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
rolling-tags:
2+
- "2025"
3+
- 2025-debian-12
4+
- 2025.3.12

‎bitnami/kes/README.md‎

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
# Bitnami Key Managament for Object Storage based on KES&reg;
2+
3+
## What is Bitnami Key Managament for Object Storage based on KES&reg;?
4+
5+
> KES is a cloud-native distributed key management and encryption server designed to secure modern applications at scale.
6+
7+
[Overview of Bitnami Key Managament for Object Storage based on KES&reg;](https://min.io/)
8+
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.
9+
10+
## TL;DR
11+
12+
```console
13+
docker run --name kes bitnami/kes:latest
14+
```
15+
16+
## Why use Bitnami Images?
17+
18+
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
19+
* With Bitnami images the latest bug fixes and features are available as soon as possible.
20+
* Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
21+
* All our images are based on [**minideb**](https://github.com/bitnami/minideb) -a minimalist Debian based container image that gives you a small base container image and the familiarity of a leading Linux distribution- or **scratch** -an explicitly empty image-.
22+
* All Bitnami images available in Docker Hub are signed with [Notation](https://notaryproject.dev/). [Check this post](https://blog.bitnami.com/2024/03/bitnami-packaged-containers-and-helm.html) to know how to verify the integrity of the images.
23+
* Bitnami container images are released on a regular basis with the latest distribution packages available.
24+
25+
Looking to use Bitnami Key Managament for Object Storage based on KES&reg; in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the commercial edition of the Bitnami catalog.
26+
27+
## Only latest stable branch maintained in the free Bitnami catalog
28+
29+
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
30+
31+
Please check the Bitnami Premium page in our partner [Arrow Electronics](https://www.arrow.com/globalecs/na/vendors/bitnami?utm_source=GitHub&utm_medium=containers) for more information.
32+
33+
## Supported tags and respective `Dockerfile` links
34+
35+
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).
36+
37+
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`.
38+
39+
Subscribe to project updates by watching the [bitnami/containers GitHub repo](https://github.com/bitnami/containers).
40+
41+
## Get this image
42+
43+
The recommended way to get the Bitnami Bitnami Key Managament for Object Storage based on KES&reg; Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/kes).
44+
45+
```console
46+
docker pull bitnami/kes:latest
47+
```
48+
49+
To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/kes/tags/) in the Docker Hub Registry.
50+
51+
```console
52+
docker pull bitnami/kes:[TAG]
53+
```
54+
55+
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.
56+
57+
```console
58+
git clone https://github.com/bitnami/containers.git
59+
cd bitnami/APP/VERSION/OPERATING-SYSTEM
60+
docker build -t bitnami/APP:latest .
61+
```
62+
63+
## Why use a non-root container?
64+
65+
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).
66+
67+
## Configuration
68+
69+
### Running commands
70+
71+
To run commands inside this container you can use `docker run`, for example to execute `kes --help` you can follow the example below:
72+
73+
```console
74+
docker run --rm --name kes bitnami/kes:latest -- --help
75+
```
76+
77+
Check the [official Bitnami Key Managament for Object Storage based on KES&reg; documentation](https://min.io/) for more information.
78+
79+
## Contributing
80+
81+
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.
82+
83+
## Issues
84+
85+
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/containers/issues/new/choose). For us to provide better support, be sure to fill the issue template.
86+
87+
## License
88+
89+
Copyright &copy; 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
90+
91+
Licensed under the Apache License, Version 2.0 (the "License");
92+
you may not use this file except in compliance with the License.
93+
You may obtain a copy of the License at
94+
95+
<http://www.apache.org/licenses/LICENSE-2.0>
96+
97+
Unless required by applicable law or agreed to in writing, software
98+
distributed under the License is distributed on an "AS IS" BASIS,
99+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
100+
See the License for the specific language governing permissions and
101+
limitations under the License.

0 commit comments

Comments
 (0)