From 5799744a497eeec75d719cacf0629ce5fc10463e Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 17 Feb 2023 17:59:00 +0100 Subject: [PATCH] [bitnami/consul] Release 1.14.4-debian-11-r7 (#24209) Signed-off-by: Bitnami Containers --- bitnami/consul/1/debian-11/Dockerfile | 14 +++++++------- .../opt/bitnami/.bitnami_components.json | 12 ++++++------ bitnami/consul/README.md | 14 ++++++-------- 3 files changed, 19 insertions(+), 21 deletions(-) diff --git a/bitnami/consul/1/debian-11/Dockerfile b/bitnami/consul/1/debian-11/Dockerfile index 839b1bdd72f7..84325cc079ab 100644 --- a/bitnami/consul/1/debian-11/Dockerfile +++ b/bitnami/consul/1/debian-11/Dockerfile @@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye ARG TARGETARCH -LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \ - org.opencontainers.image.description="Application packaged by Bitnami" \ +LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \ + org.opencontainers.image.created="2023-02-17T14:10:34Z" \ + org.opencontainers.image.description="Application packaged by VMware, Inc" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="1.14.4-debian-11-r6" \ - org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/consul" \ + org.opencontainers.image.ref.name="1.14.4-debian-11-r7" \ org.opencontainers.image.title="consul" \ org.opencontainers.image.vendor="VMware, Inc." \ org.opencontainers.image.version="1.14.4" @@ -22,9 +22,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"] RUN install_packages ca-certificates curl iproute2 procps zlib1g-dev RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \ COMPONENTS=( \ - "render-template-1.0.5-0-linux-${OS_ARCH}-debian-11" \ - "gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \ - "consul-1.14.4-0-linux-${OS_ARCH}-debian-11" \ + "render-template-1.0.5-1-linux-${OS_ARCH}-debian-11" \ + "gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \ + "consul-1.14.4-1-linux-${OS_ARCH}-debian-11" \ ) && \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ diff --git a/bitnami/consul/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/consul/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json index ac7f23f2f28f..11f2c6c96c64 100644 --- a/bitnami/consul/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json +++ b/bitnami/consul/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json @@ -1,23 +1,23 @@ { "consul": { "arch": "amd64", - "digest": "778dd6b1474d722c166d8ecab80a4044aafb0ee41d255eb8a10a936c25725a12", + "digest": "9674ab205c2e8a897c1e3e04adf52c3dcc448f0830ee36926f68634c336ef4d7", "distro": "debian-11", "type": "NAMI", - "version": "1.14.4-0" + "version": "1.14.4-1" }, "gosu": { "arch": "amd64", - "digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b", + "digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa", "distro": "debian-11", "type": "NAMI", - "version": "1.16.0-1" + "version": "1.16.0-2" }, "render-template": { "arch": "amd64", - "digest": "57c1d857acbb187fcb98f4ba26d138af9d866f59ad38dd443a75c0a6422de994", + "digest": "185e277977366ec222d2bde1a395ffa138ce1a9d3bdf1df20c3e49e8b8f9c68b", "distro": "debian-11", "type": "NAMI", - "version": "1.0.5-0" + "version": "1.0.5-1" } } \ No newline at end of file diff --git a/bitnami/consul/README.md b/bitnami/consul/README.md index 529e8c00f869..09ade6bfd53e 100644 --- a/bitnami/consul/README.md +++ b/bitnami/consul/README.md @@ -121,7 +121,7 @@ docker run --name consul-node1 --network consul-network bitnami/consul:latest We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network. -### Using Docker Compose +### 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 consul-network. @@ -152,13 +152,11 @@ Then, launch the containers using: docker-compose up -d ``` -## Setting up a cluster - -### Docker Compose deployment +## Setting up a cluster using Docker Compose This is the simplest way to run HashiCorp Consul with clustering configuration: -#### Step 1: Add a server node in your `docker-compose.yml` +### Step 1: Add a server node in your `docker-compose.yml` Copy the snippet below into your docker-compose.yml to add a HashiCorp Consul server node to your cluster configuration. @@ -186,7 +184,7 @@ services: > **Note:** The value of the **CONSUL_BOOTSTRAP_EXPECT** should reflect the total number of nodes the cluster will have. -##### Step 2: Add extra nodes to your configuration +### Step 2: Add extra nodes to your configuration Update the definitions for nodes you want your HashiCorp Consul node cluster with. If it is a remote WAN node, use `CONSUL_RETRY_JOIN_WAN_ADDRESS`. @@ -214,7 +212,7 @@ consul-node3: - 'consul-node3_data:/bitnami' ``` -##### Step 3: Add the volume description +### Step 3: Add the volume description ```yaml volumes: @@ -386,7 +384,7 @@ This command will generate a keygen, that you can add to your Dockerfile, docker docker run -e CONSUL_GOSSIP_ENCRYPTION_KEY=YOUR_GENERATED_KEY --name consul bitnami/consul:latest ``` -#### Using Docker Compose deployment +#### Deploying a Docker Compose file ```yaml consul: