From 694b98c02ca7f7d6c69720954b01f25695d3e65d Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 6 Mar 2026 17:26:08 +0100 Subject: [PATCH] [bitnami/etcd] Release 3.6.8-debian-12-r2 (#91374) Signed-off-by: Bitnami Bot --- bitnami/etcd/3.6/debian-12/Dockerfile | 8 +- bitnami/etcd/README.md | 118 +++----------------------- 2 files changed, 16 insertions(+), 110 deletions(-) diff --git a/bitnami/etcd/3.6/debian-12/Dockerfile b/bitnami/etcd/3.6/debian-12/Dockerfile index 5304bf9eff8d..37208838d067 100644 --- a/bitnami/etcd/3.6/debian-12/Dockerfile +++ b/bitnami/etcd/3.6/debian-12/Dockerfile @@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-02-19T01:28:04Z" \ + org.opencontainers.image.created="2026-03-06T16:11:40Z" \ 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.52.4-0-linux-${OS_ARCH}-debian-12" \ - "etcd-3.6.8-0-linux-${OS_ARCH}-debian-12" \ + "yq-4.52.4-1-linux-${OS_ARCH}-debian-12" \ + "etcd-3.6.8-1-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.6.8" \ BITNAMI_APP_NAME="etcd" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="2" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/etcd/bin:$PATH" EXPOSE 2379 2380 diff --git a/bitnami/etcd/README.md b/bitnami/etcd/README.md index 0725bb13f368..6d9b1d941dd7 100644 --- a/bitnami/etcd/README.md +++ b/bitnami/etcd/README.md @@ -1,7 +1,5 @@ # Bitnami Secure Image for Etcd -## What is 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/) @@ -44,10 +42,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t > Please note ARM support in branch 3.4 is experimental/unstable according to [upstream docs](https://github.com/etcd-io/website/blob/main/content/en/docs/v3.4/op-guide/supported-platform.md), therefore branch 3.4 is only supported for AMD archs while branch 3.5 supports multiarch (AMD and ARM) -## Prerequisites - -To run this application you need [Docker Engine](https://www.docker.com/products/docker-engine) >= `1.10.0`. [Docker Compose](https://docs.docker.com/compose/) is recommended with a version `1.6.0` or later. - ## Get this image The recommended way to get the Bitnami Etcd Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/etcd). @@ -72,107 +66,19 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` +## Using `docker-compose.yaml` + +Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/etcd). + ## 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. Containers attached to the same network can communicate with each other using the container name as the hostname. -### Using the Command Line - -In this example, we will create a Etcd client instance that will connect to the server instance that is running on the same docker network as the client. - -#### Step 1: Create a network - -```console -docker network create app-tier --driver bridge -``` - -#### Step 2: Launch the Etcd server instance - -Use the `--network app-tier` argument to the `docker run` command to attach the Etcd container to the `app-tier` network. - -```console -docker run -d --name Etcd-server \ - --network app-tier \ - --publish 2379:2379 \ - --publish 2380:2380 \ - --env ALLOW_NONE_AUTHENTICATION=yes \ - --env ETCD_ADVERTISE_CLIENT_URLS=http://etcd-server:2379 \ - bitnami/etcd:latest -``` - -#### Step 3: Launch your Etcd client instance - -Finally we create a new container instance to launch the Etcd client and connect to the server created in the previous step: - -```console -docker run -it --rm \ - --network app-tier \ - --env ALLOW_NONE_AUTHENTICATION=yes \ - bitnami/etcd:latest etcdctl --endpoints http://etcd-server:2379 put /message Hello -``` - -### Using a Docker Compose file - -When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the Etcd server from your own custom application image which is identified in the following snippet by the service name `myapp`. - -```yaml -version: '2' - -networks: - app-tier: - driver: bridge - -services: - Etcd: - image: bitnami/etcd:latest - environment: - - ALLOW_NONE_AUTHENTICATION=yes - - ETCD_ADVERTISE_CLIENT_URLS=http://etcd:2379 - ports: - - 2379:2379 - - 2380:2380 - networks: - - app-tier - myapp: - image: YOUR_APPLICATION_IMAGE - networks: - - app-tier -``` - -> **IMPORTANT**: -> -> 1. Please update the placeholder `YOUR_APPLICATION_IMAGE` in the above snippet with your application image -> 2. In your application container, use the hostname `etcd` to connect to the Etcd server - -Launch the containers using: - -```console -docker-compose up -d -``` - ## Configuration -The configuration can easily be setup by mounting your own configuration file on the directory `/opt/bitnami/etcd/conf`: - -```console -docker run --name Etcd -v /path/to/Etcd.conf.yml:/opt/bitnami/Etcd/conf/etcd.conf.yml bitnami/etcd:latest -``` - -After that, your configuration will be taken into account in the server's behaviour. - -You can also do this by changing the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/etcd/docker-compose.yml) file present in this repository: - -```yaml -Etcd: - ... - volumes: - - /path/to/Etcd.conf.yml:/opt/bitnami/etcd/conf/etcd.conf.yml - ... -``` - -You can find a sample configuration file on this [link](https://github.com/coreos/etcd/blob/master/etcd.conf.yml.sample) +The following section describes the supported environment variables ### Environment variables @@ -225,7 +131,13 @@ Apart from providing your custom configuration file, you can also modify the ser | `ETCD_DAEMON_USER` | etcd system user name. | `etcd` | | `ETCD_DAEMON_GROUP` | etcd system user group. | `etcd` | -Additionally, you can configure etcd using the upstream env variables [here](https://etcd.io/docs/v3.4/op-guide/configuration/) +Additionally, you can configure etcd using the upstream env variables [here](https://etcd.io/docs/v3.6/op-guide/configuration/) + +### Configuration file + +The configuration can easily be setup by mounting your own configuration file on the directory `/opt/bitnami/etcd/conf`: + +You can find a sample configuration file on this [link](https://github.com/coreos/etcd/blob/master/etcd.conf.yml.sample) ### FIPS configuration in Bitnami Secure Images @@ -259,12 +171,6 @@ The Bitnami Etcd Docker image from the [Bitnami Secure Images](https://go-vmware For further documentation, please check [Etcd documentation](https://coreos.com/etcd/docs/latest/) or its [GitHub repository](https://github.com/coreos/etcd) -## Using `docker-compose.yaml` - -Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/etcd). - -If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md). - ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.