public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

1.11.5-debian-10-r6 release

This commit is contained in:
Bitnami Bot 2022-04-20 09:42:12 +00:00 committed by Bitnami Containers
parent 86ce604b47
commit 5f0962321b
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/consul/README.md
View File

@ -32,9 +32,6 @@ You can find the available configuration options in the [Environment Variables](
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released daily with the latest distribution packages available.
> This [CVE scan report](https://quay.io/repository/bitnami/consul?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
## How to deploy HashiCorp Consul 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 HashiCorp Consul Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/consul).
@ -50,7 +47,7 @@ Non-root container images add an extra layer of security and are generally recom
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`1`, `1-debian-10`, `1.11.5`, `1.11.5-debian-10-r5`, `latest` (1/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-consul/blob/1.11.5-debian-10-r5/1/debian-10/Dockerfile)
* [`1`, `1-debian-10`, `1.11.5`, `1.11.5-debian-10-r6`, `latest` (1/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-consul/blob/1.11.5-debian-10-r6/1/debian-10/Dockerfile)
Subscribe to project updates by watching the [bitnami/consul GitHub repo](https://github.com/bitnami/bitnami-docker-consul).
@ -491,7 +488,6 @@ Also, some env var changes have been performed maintaining backward compatibilit
| `CONSUL_AGENT_MODE` | `CONSUL_SERVER_MODE` |
| `CONSUL_RETRY_JOIN_ADDRESS` | `CONSUL_RETRY_JOIN` |
### 1.4.0-r16
- The Consul container has been migrated to a non-root user approach. Previously the container ran as the `root` user and the Consul daemon was started as the `consul` user. From now on, both the container and the Consul daemon run as user `1001`. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile.