[bitnami/etcd] Release 3.7.1-debian-12-r1 (#96456)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-08-14 12:43:54 +02:00
committed by GitHub
parent 2eed6f41b4
commit 4fe4262ed2
10 changed files with 45 additions and 45 deletions
+4 -4
View File
@@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="https://downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-07-23T22:26:15Z" \
org.opencontainers.image.created="2026-08-14T10:25:46Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/etcd/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/etcd" \
@@ -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=( \
"yq-4.53.3-2-linux-${OS_ARCH}-debian-12" \
"etcd-3.7.1-0-linux-${OS_ARCH}-debian-12" \
"yq-4.53.3-3-linux-${OS_ARCH}-debian-12" \
"etcd-3.7.1-2-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -50,7 +50,7 @@ COPY rootfs /
RUN /opt/bitnami/scripts/etcd/postunpack.sh
ENV APP_VERSION="3.7.1" \
BITNAMI_APP_NAME="etcd" \
IMAGE_REVISION="0" \
IMAGE_REVISION="1" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/etcd/bin:$PATH"
EXPOSE 2379 2380
@@ -1 +0,0 @@
df3700bdba886a032a432293c2ae765f8a9965b6fccb3ca986029306cd517fdc etcd-3.7.1-0-linux-amd64-debian-12.tar.gz
@@ -1 +0,0 @@
03360e122e8cf82cf7a5d8dfcf7f6304d2c548a3c415522adfeb2e974601f942 etcd-3.7.1-0-linux-arm64-debian-12.tar.gz
@@ -0,0 +1 @@
51d8e21edfa1f57969943f2922dc3cfa251905834afbe0450d15a389ca8b53bd etcd-3.7.1-2-linux-amd64-debian-12.tar.gz
@@ -0,0 +1 @@
89710470c5da80c219eedc58481a3f504e2eef16842b5c9e55a25bc18e754f3b etcd-3.7.1-2-linux-arm64-debian-12.tar.gz
@@ -1 +0,0 @@
d7cb02bda9fa20f362656577296b535e338710f43057803014a124d344b0be04 yq-4.53.3-2-linux-amd64-debian-12.tar.gz
@@ -1 +0,0 @@
bbe968c785b1dad4c8ce87248b6770bb779bb7e72b3338a3a123a9c2602712f8 yq-4.53.3-2-linux-arm64-debian-12.tar.gz
@@ -0,0 +1 @@
629aa578b8aad3df67f2bd63cf90536bdbef09d104a861577e52fb6b860d954b yq-4.53.3-3-linux-amd64-debian-12.tar.gz
@@ -0,0 +1 @@
cd594154ab6853f508cfaefeed74676bc2f5c65efe910096ca3a664c050e67f5 yq-4.53.3-3-linux-arm64-debian-12.tar.gz
+37 -37
View File
@@ -1,8 +1,8 @@
# Bitnami Secure Image for Etcd
# Bitnami Secure Image for etcd
> etcd is a distributed key-value store designed to securely store data across a cluster. etcd is widely used in production on account of its reliability, fault-tolerance and ease of use.
[Overview of Etcd](https://etcd.io/)
[Overview of etcd](https://etcd.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.
## TL;DR
@@ -36,9 +36,9 @@ 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).
## How to deploy Etcd in Kubernetes?
## How to deploy etcd in Kubernetes?
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Etcd Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/etcd).
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami etcd Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/etcd).
## Why use a non-root container?
@@ -50,11 +50,11 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
## Get this image
The Bitnami Etcd Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
The Bitnami etcd Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## Connecting to other containers
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a Etcd server running inside a container can easily be accessed by your application containers using a Etcd client.
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a etcd server running inside a container can easily be accessed by your application containers using a etcd client.
Containers attached to the same network can communicate with each other using the container name as the hostname.
@@ -68,34 +68,34 @@ Apart from providing your custom configuration file, you can also modify the ser
#### Customizable environment variables
| Name | Description | Default Value |
|------------------------------------|----------------------------------------------------------------------------------------------|-------------------------|
| `ETCD_SNAPSHOTS_DIR` | etcd snapshots directory (used on "disaster recovery" feature). | `/snapshots` |
| `ETCD_SNAPSHOT_HISTORY_LIMIT` | etcd snapshots history limit. | `1` |
| `ETCD_INIT_SNAPSHOTS_DIR` | etcd init snapshots directory (used on "init from snapshot" feature). | `/init-snapshot` |
| `ALLOW_NONE_AUTHENTICATION` | Allow accessing etcd without any password. | `no` |
| `ETCD_ROOT_PASSWORD` | Password for the etcd root user. | `nil` |
| `ETCD_CLUSTER_DOMAIN` | Domain to use to discover other etcd members. | `nil` |
| `ETCD_START_FROM_SNAPSHOT` | Whether etcd should start from an existing snapshot or not. | `no` |
| `ETCD_DISASTER_RECOVERY` | Whether etcd should try or not to recover from snapshots when the cluste disastrously fails. | `no` |
| `ETCD_ON_K8S` | Whether etcd is running on a K8s environment or not. | `no` |
| `ETCD_INIT_SNAPSHOT_FILENAME` | Existing snapshot filename to start the etcd cluster from. | `nil` |
| `ETCD_PREUPGRADE_START_DELAY` | Optional delay before starting the pre-upgrade hook (in seconds). | `nil` |
| `ETCD_NAME` | etcd member name. | `nil` |
| `ETCD_LOG_LEVEL` | etcd log level. | `info` |
| `ETCD_LISTEN_CLIENT_URLS` | List of URLs to listen on for client traffic. | `http://0.0.0.0:2379` |
| `ETCD_ADVERTISE_CLIENT_URLS` | List of this member client URLs to advertise to the rest of the cluster. | `http://127.0.0.1:2379` |
| `ETCD_INITIAL_CLUSTER` | Initial list of members to bootstrap a cluster. | `nil` |
| `ETCD_LISTEN_PEER_URLS` | List of URLs to listen on for peers traffic. | `nil` |
| `ETCD_INITIAL_ADVERTISE_PEER_URLS` | List of this member peer URLs to advertise to the rest of the cluster while bootstrapping. | `nil` |
| `ETCD_INITIAL_CLUSTER_TOKEN` | Unique initial cluster token used for bootstrapping. | `nil` |
| `ETCD_AUTO_TLS` | Use generated certificates for TLS communications with clients. | `false` |
| `ETCD_CERT_FILE` | Path to the client server TLS cert file. | `nil` |
| `ETCD_KEY_FILE` | Path to the client server TLS key file. | `nil` |
| `ETCD_TRUSTED_CA_FILE` | Path to the client server TLS trusted CA cert file. | `nil` |
| `ETCD_CLIENT_CERT_AUTH` | Enable client cert authentication | `false` |
| `ETCD_PEER_AUTO_TLS` | Use generated certificates for TLS communications with peers. | `false` |
| `ETCD_EXTRA_AUTH_FLAGS` | Comma separated list of authentication flags to append to etcdctl | `nil` |
| Name | Description | Default Value |
|------------------------------------|-----------------------------------------------------------------------------------------------|-------------------------|
| `ETCD_SNAPSHOTS_DIR` | etcd snapshots directory (used on "disaster recovery" feature). | `/snapshots` |
| `ETCD_SNAPSHOT_HISTORY_LIMIT` | etcd snapshots history limit. | `1` |
| `ETCD_INIT_SNAPSHOTS_DIR` | etcd init snapshots directory (used on "init from snapshot" feature). | `/init-snapshot` |
| `ALLOW_NONE_AUTHENTICATION` | Allow accessing etcd without any password. | `no` |
| `ETCD_ROOT_PASSWORD` | Password for the etcd root user. | `nil` |
| `ETCD_CLUSTER_DOMAIN` | Domain to use to discover other etcd members. | `nil` |
| `ETCD_START_FROM_SNAPSHOT` | Whether etcd should start from an existing snapshot or not. | `no` |
| `ETCD_DISASTER_RECOVERY` | Whether etcd should try or not to recover from snapshots when the cluster disastrously fails. | `no` |
| `ETCD_ON_K8S` | Whether etcd is running on a K8s environment or not. | `no` |
| `ETCD_INIT_SNAPSHOT_FILENAME` | Existing snapshot filename to start the etcd cluster from. | `nil` |
| `ETCD_PREUPGRADE_START_DELAY` | Optional delay before starting the pre-upgrade hook (in seconds). | `nil` |
| `ETCD_NAME` | etcd member name. | `nil` |
| `ETCD_LOG_LEVEL` | etcd log level. | `info` |
| `ETCD_LISTEN_CLIENT_URLS` | List of URLs to listen on for client traffic. | `http://0.0.0.0:2379` |
| `ETCD_ADVERTISE_CLIENT_URLS` | List of this member client URLs to advertise to the rest of the cluster. | `http://127.0.0.1:2379` |
| `ETCD_INITIAL_CLUSTER` | Initial list of members to bootstrap a cluster. | `nil` |
| `ETCD_LISTEN_PEER_URLS` | List of URLs to listen on for peers traffic. | `nil` |
| `ETCD_INITIAL_ADVERTISE_PEER_URLS` | List of this member peer URLs to advertise to the rest of the cluster while bootstrapping. | `nil` |
| `ETCD_INITIAL_CLUSTER_TOKEN` | Unique initial cluster token used for bootstrapping. | `nil` |
| `ETCD_AUTO_TLS` | Use generated certificates for TLS communications with clients. | `false` |
| `ETCD_CERT_FILE` | Path to the client server TLS cert file. | `nil` |
| `ETCD_KEY_FILE` | Path to the client server TLS key file. | `nil` |
| `ETCD_TRUSTED_CA_FILE` | Path to the client server TLS trusted CA cert file. | `nil` |
| `ETCD_CLIENT_CERT_AUTH` | Enable client cert authentication | `false` |
| `ETCD_PEER_AUTO_TLS` | Use generated certificates for TLS communications with peers. | `false` |
| `ETCD_EXTRA_AUTH_FLAGS` | Comma separated list of authentication flags to append to etcdctl | `nil` |
#### Read-only environment variables
@@ -123,7 +123,7 @@ You can find a sample configuration file on this [link](https://github.com/coreo
### FIPS configuration in Bitnami Secure Images
The Bitnami Etcd 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:
The Bitnami etcd 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`.
- `GODEBUG`: controls Go FIPS mode. Use `fips140=only` (restricted), `fips140=on` (relaxed), or `fips140=off` (disabled).
@@ -140,7 +140,7 @@ The Bitnami Etcd Docker image from the [Bitnami Secure Images](https://go-vmware
### 3.4.15-debian-10-r7
- The container now contains the needed logic to deploy the Etcd container on Kubernetes using the [Bitnami Etcd Chart](https://github.com/bitnami/charts/tree/master/bitnami/etcd).
- The container now contains the needed logic to deploy the etcd container on Kubernetes using the [Bitnami etcd Chart](https://github.com/bitnami/charts/tree/master/bitnami/etcd).
### 3.4.13-debian-10-r7
@@ -152,7 +152,7 @@ The Bitnami Etcd Docker image from the [Bitnami Secure Images](https://go-vmware
## Further documentation
For further documentation, please check [Etcd documentation](https://coreos.com/etcd/docs/latest/) or its [GitHub repository](https://github.com/coreos/etcd)
For further documentation, please check [etcd documentation](https://coreos.com/etcd/docs/latest/) or its [GitHub repository](https://github.com/coreos/etcd)
## License