diff --git a/bitnami/concourse/README.md b/bitnami/concourse/README.md index 432bf03cd1d0..11e0e185cc74 100644 --- a/bitnami/concourse/README.md +++ b/bitnami/concourse/README.md @@ -6,8 +6,6 @@ [Overview of Concourse](https://concourse-ci.org/) - - ## TL;DR ```console diff --git a/bitnami/harbor-core/README.md b/bitnami/harbor-core/README.md index 04a11e47d5f9..b079c2a3b122 100644 --- a/bitnami/harbor-core/README.md +++ b/bitnami/harbor-core/README.md @@ -6,8 +6,6 @@ [Overview of Harbor Core](https://goharbor.io/) - - ## TL;DR ```console diff --git a/bitnami/harbor-exporter/README.md b/bitnami/harbor-exporter/README.md index 284a7b344273..689b19531ee0 100644 --- a/bitnami/harbor-exporter/README.md +++ b/bitnami/harbor-exporter/README.md @@ -6,8 +6,6 @@ [Overview of harbor-exporter](https://github.com/goharbor/harbor) - - ## TL;DR This container is part of the [Harbor solution](https://github.com/bitnami/charts/tree/main/bitnami/harbor) that is primarily intended to be deployed in Kubernetes. You can deploy Harbor solution and then enable this specific container with the command below: diff --git a/bitnami/harbor-jobservice/README.md b/bitnami/harbor-jobservice/README.md index 64b0d62b3f55..4758bd999502 100644 --- a/bitnami/harbor-jobservice/README.md +++ b/bitnami/harbor-jobservice/README.md @@ -6,8 +6,6 @@ [Overview of Harbor Job Service](https://github.com/goharbor/harbor) - - ## TL;DR ```console diff --git a/bitnami/harbor-registry/README.md b/bitnami/harbor-registry/README.md index bef1c0ed3b70..58e3b1827479 100644 --- a/bitnami/harbor-registry/README.md +++ b/bitnami/harbor-registry/README.md @@ -6,8 +6,6 @@ [Overview of Harbor Registry](https://github.com/goharbor/harbor) - - ## TL;DR ```console diff --git a/bitnami/harbor-registryctl/README.md b/bitnami/harbor-registryctl/README.md index d12578f55caf..8cbdaf959ee0 100644 --- a/bitnami/harbor-registryctl/README.md +++ b/bitnami/harbor-registryctl/README.md @@ -6,8 +6,6 @@ [Overview of Harbor Registryctl](https://github.com/goharbor/harbor) - - ## TL;DR ```console diff --git a/bitnami/jaeger/README.md b/bitnami/jaeger/README.md index 5d92f49a6fb4..6cee52dc08c5 100644 --- a/bitnami/jaeger/README.md +++ b/bitnami/jaeger/README.md @@ -6,8 +6,6 @@ [Overview of jaeger](https://www.jaegertracing.io/) - - ## TL;DR ```console diff --git a/bitnami/jenkins-agent/README.md b/bitnami/jenkins-agent/README.md index 4b887c0a9bf7..b6ba1a7f2525 100644 --- a/bitnami/jenkins-agent/README.md +++ b/bitnami/jenkins-agent/README.md @@ -11,7 +11,7 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema ## TL;DR ```console -$ docker run --name jenkins-agent --env JENKINS_URL=http://jenkins:port bitnami/jenkins-agent:latest +docker run --name jenkins-agent --env JENKINS_URL=http://jenkins:port bitnami/jenkins-agent:latest ``` You can find all the available configuration options in the [Environment Variables](#environment-variables) section. @@ -42,21 +42,21 @@ Subscribe to project updates by watching the [bitnami/containers GitHub repo](ht The recommended way to get the Bitnami Jenkins Agent Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/jenkins). ```console -$ docker pull bitnami/jenkins-agent:latest +docker pull bitnami/jenkins-agent:latest ``` 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/jenkins/tags/) in the Docker Hub Registry. ```console -$ docker pull bitnami/jenkins-agent:[TAG] +docker pull bitnami/jenkins-agent:[TAG] ``` 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. ```console -$ git clone https://github.com/bitnami/containers.git -$ cd bitnami/APP/VERSION/OPERATING-SYSTEM -$ docker build -t bitnami/APP:latest . +git clone https://github.com/bitnami/containers.git +cd bitnami/APP/VERSION/OPERATING-SYSTEM +docker build -t bitnami/APP:latest . ``` ## Configuration @@ -65,7 +65,7 @@ $ docker build -t bitnami/APP:latest . When you start the Jenkins Agent image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. If you want to add a new environment variable: -- For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/jenkins/docker-compose.yml) file present in this repository: +* For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/jenkins/docker-compose.yml) file present in this repository: ```yaml jenkins-agent: @@ -75,7 +75,7 @@ When you start the Jenkins Agent image, you can adjust the configuration of the ... ``` -- For manual execution add a `--env` option with each variable and value: +* For manual execution add a `--env` option with each variable and value: ```console $ docker run -d --name jenkins-agent \ @@ -85,35 +85,35 @@ When you start the Jenkins Agent image, you can adjust the configuration of the Available environment variables: -##### User and Site configuration +#### User and Site configuration -- `JENKINS_AGENT_WORKDIR`: The working directory of the remoting instance (stores cache and logs by default). Default: **/bitnami/jenkins/home** -- `JENKINS_URL`: Specify the Jenkins root URLs to connect to. -- `JENKINS_AGENT_TUNNEL`: Connect to the specified host and port, instead of connecting directly to Jenkins. Useful when connection to Jenkins needs to be tunneled. -- `JENKINS_AGENT_PROTOCOLS`: Specify the remoting protocols to attempt when instanceIdentity is provided. -- `JENKINS_AGENT_DIRECT_CONNECTION`: Connect directly to this TCP agent port, skipping the HTTP(S) connection. -- `JENKINS_AGENT_INSTANCE_IDENTITY`: The base64 encoded InstanceIdentity byte array of the Jenkins controller. -- `JENKINS_AGENT_WEB_SOCKET`: Make a WebSocket connection to Jenkins rather than using the TCP port. Default: **false** -- `JENKINS_AGENT_SECRET`: Jenkins Agent name. -- `JENKINS_AGENT_NAME`: Jenkins Agent secret. +* `JENKINS_AGENT_WORKDIR`: The working directory of the remoting instance (stores cache and logs by default). Default: **/bitnami/jenkins/home** +* `JENKINS_URL`: Specify the Jenkins root URLs to connect to. +* `JENKINS_AGENT_TUNNEL`: Connect to the specified host and port, instead of connecting directly to Jenkins. Useful when connection to Jenkins needs to be tunneled. +* `JENKINS_AGENT_PROTOCOLS`: Specify the remoting protocols to attempt when instanceIdentity is provided. +* `JENKINS_AGENT_DIRECT_CONNECTION`: Connect directly to this TCP agent port, skipping the HTTP(S) connection. +* `JENKINS_AGENT_INSTANCE_IDENTITY`: The base64 encoded InstanceIdentity byte array of the Jenkins controller. +* `JENKINS_AGENT_WEB_SOCKET`: Make a WebSocket connection to Jenkins rather than using the TCP port. Default: **false** +* `JENKINS_AGENT_SECRET`: Jenkins Agent name. +* `JENKINS_AGENT_NAME`: Jenkins Agent secret. -##### JAVA configuration +#### JAVA configuration -- `JAVA_OPTS`: Customize JVM parameters. No defaults. -- `JAVA_HOME`: Java Home directory. Default: **/opt/bitnami/java** +* `JAVA_OPTS`: Customize JVM parameters. No defaults. +* `JAVA_HOME`: Java Home directory. Default: **/opt/bitnami/java** ## Logging The Bitnami Jenkins Agent Docker image sends the container logs to `stdout`. To view the logs: ```console -$ docker logs jenkins +docker logs jenkins ``` Or using Docker Compose: ```console -$ docker-compose logs jenkins +docker-compose logs jenkins ``` You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. @@ -150,7 +150,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, diff --git a/bitnami/keycloak/README.md b/bitnami/keycloak/README.md index 4f1c78541515..63e5281151bb 100644 --- a/bitnami/keycloak/README.md +++ b/bitnami/keycloak/README.md @@ -86,7 +86,7 @@ The Bitnami Keycloak container can create a default admin user by setting the fo The Bitnami Keycloak container can connect to a database by setting the following environment variables: -- `KEYCLOAK_DATABASE_VENDOR`: Database vendor. Default: **postgres**. Use **dev-mem** or **dev-file** to use an in-memory or file-based database for development purposes. +* `KEYCLOAK_DATABASE_VENDOR`: Database vendor. Default: **postgres**. Use **dev-mem** or **dev-file** to use an in-memory or file-based database for development purposes. ### PostgreSQL database connection configuration diff --git a/bitnami/kubeapps-apprepository-controller/README.md b/bitnami/kubeapps-apprepository-controller/README.md index 8c824e05af9a..a9ea9dd0f5a9 100644 --- a/bitnami/kubeapps-apprepository-controller/README.md +++ b/bitnami/kubeapps-apprepository-controller/README.md @@ -6,8 +6,6 @@ [Overview of Kubeapps AppRepository Controller](https://github.com/vmware-tanzu/kubeapps) - - ## TL;DR ```console diff --git a/bitnami/kubeapps-asset-syncer/README.md b/bitnami/kubeapps-asset-syncer/README.md index ffc3315a8a90..85edccb74138 100644 --- a/bitnami/kubeapps-asset-syncer/README.md +++ b/bitnami/kubeapps-asset-syncer/README.md @@ -6,8 +6,6 @@ [Overview of Kubeapps Asset Syncer](https://github.com/vmware-tanzu/kubeapps) - - ## TL;DR ```console diff --git a/bitnami/mariadb-galera/README.md b/bitnami/mariadb-galera/README.md index faf422748688..e5d64c1476d6 100644 --- a/bitnami/mariadb-galera/README.md +++ b/bitnami/mariadb-galera/README.md @@ -679,7 +679,7 @@ docker-compose up mariadb ## Notable Changes -### 10.2.41-debian-10-r11, 10.3.32-debian-10-r11, 10.4.22-debian-10-r11, 10.5.13-debian-10-r10, 10.6.5-debian-10-r10, 10.3.38-r6-debian-11, 10.4.28-r6-debian-11, 10.5.19-r5-debian-11, 10.6.12-r5-debian-11, 10.7.8-r5-debian-11, 10.8.7-r5-debian-11, 10.9.5-r5-debian-11 and 10.10.3-r5-debian-11 +### 10.2.41-debian-10-r11, 10.3.32-debian-10-r11, 10.4.22-debian-10-r11, 10.5.13-debian-10-r10, 10.6.5-debian-10-r10, 10.3.38-r6-debian-11, 10.4.28-r6-debian-11, 10.5.19-r5-debian-11, 10.6.12-r5-debian-11, 10.7.8-r5-debian-11, 10.8.7-r5-debian-11, 10.9.5-r5-debian-11 and 10.10.3-r5-debian-11 * The command `mysql_upgrade` no longer includes the flag `--force`. Nonetheless, it can be enabled by using the [mysql_upgrade] option group in the MariaDB configuration. diff --git a/bitnami/mariadb/README.md b/bitnami/mariadb/README.md index 2aba3b381799..facfffdc817a 100644 --- a/bitnami/mariadb/README.md +++ b/bitnami/mariadb/README.md @@ -651,7 +651,7 @@ docker-compose up mariadb ## Notable Changes -### 10.2.41-debian-10-r12, 10.3.32-debian-10-r13, 10.4.22-debian-10-r13, 10.5.13-debian-10-r14, 10.6.5-debian-10-r13, 10.3.38-r5-debian-11, 10.4.28-r5-debian-11, 10.5.19-r5-debian-11, 10.6.12-r5-debian-11, 10.7.8-r5-debian-11, 10.8.7-r5-debian-11, 10.9.5-r5-debian-11 and 10.10.3-r6-debian-11 +### 10.2.41-debian-10-r12, 10.3.32-debian-10-r13, 10.4.22-debian-10-r13, 10.5.13-debian-10-r14, 10.6.5-debian-10-r13, 10.3.38-r5-debian-11, 10.4.28-r5-debian-11, 10.5.19-r5-debian-11, 10.6.12-r5-debian-11, 10.7.8-r5-debian-11, 10.8.7-r5-debian-11, 10.9.5-r5-debian-11 and 10.10.3-r6-debian-11 * The command `mysql_upgrade` no longer includes the flag `--force`. Nonetheless, it can be enabled by using the [mysql_upgrade] option group in the MariaDB configuration. diff --git a/bitnami/multus-cni/README.md b/bitnami/multus-cni/README.md index 1f2b9fc68543..2f42f0ab3484 100644 --- a/bitnami/multus-cni/README.md +++ b/bitnami/multus-cni/README.md @@ -2,7 +2,7 @@ ## What is Multus CNI? -> Multus is a CNI plugin for Kubernetes clusters. Written in Go, features adding multiple network interfaces to pods. +> Multus is a CNI plugin for Kubernetes clusters. Written in Go, features adding multiple network interfaces to pods. [Overview of Multus CNI](https://github.com/k8snetworkplumbingwg/multus-cni) diff --git a/bitnami/pgbouncer/README.md b/bitnami/pgbouncer/README.md index 1f7c7038edc4..82f678eabee4 100644 --- a/bitnami/pgbouncer/README.md +++ b/bitnami/pgbouncer/README.md @@ -127,7 +127,7 @@ To expose the same database name as the backend, set `PGBOUNCER_DATABASE="$POSTG * `PGBOUNCER_DEFAULT_POOL_SIZE` : PgBouncer maximum server connections to allow per user/database pair. Default: **20**. * `PGBOUNCER_MIN_POOL_SIZE` : PgBouncer has at least this amount of open connections. Default: **0 (disabled)**. * `PGBOUNCER_RESERVE_POOL_SIZE` : PgBouncer allows this amount of additional connections. Default: **0 (disabled)**. -* `PGBOUNCER_IGNORE_STARTUP_PARAMETERS`: you can use this to set `ignore_startup_parameters` in the auto-generated `pgbouncer.ini`. This can be useful for solving certain connection issues. See https://www.pgbouncer.org/config.html for more details. +* `PGBOUNCER_IGNORE_STARTUP_PARAMETERS`: you can use this to set `ignore_startup_parameters` in the auto-generated `pgbouncer.ini`. This can be useful for solving certain connection issues. See for more details. * `PGBOUNCER_SERVER_IDLE_TIMEOUT`: PgBouncer maximum time in seconds a server connection can be idle. If 0 then the timeout is disabled. Default: **600** * `PGBOUNCER_SERVER_RESET_QUERY`: PgBouncer query sent to server on connection release before making it available to other clients. Default: **DISCARD ALL** * `PGBOUNCER_STATS_USERS`: PgBouncer comma-separated list of database users that are allowed to connect and run read-only queries. No defaults. diff --git a/bitnami/sealed-secrets/README.md b/bitnami/sealed-secrets/README.md index 5516ca5e4d33..239b976a94d7 100644 --- a/bitnami/sealed-secrets/README.md +++ b/bitnami/sealed-secrets/README.md @@ -6,8 +6,6 @@ [Overview of Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets) - - ## TL;DR ```console diff --git a/bitnami/spark/README.md b/bitnami/spark/README.md index c82c4e171136..86914d97d185 100644 --- a/bitnami/spark/README.md +++ b/bitnami/spark/README.md @@ -195,7 +195,7 @@ RUN curl https://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk-bundle/1.11.7 In a similar way that in the previous section, you may want to use a different version of Hadoop jars. -Go to https://spark.apache.org/downloads.html and copy the download url bundling the Hadoop version you want and matching the Apache Spark version of the container. Extend the Bitnami container image as below: +Go to and copy the download url bundling the Hadoop version you want and matching the Apache Spark version of the container. Extend the Bitnami container image as below: ```Dockerfile FROM bitnami/spark:3.0.0 diff --git a/bitnami/wavefront-hpa-adapter/README.md b/bitnami/wavefront-hpa-adapter/README.md index 01c56b8a131d..53c3fea60764 100644 --- a/bitnami/wavefront-hpa-adapter/README.md +++ b/bitnami/wavefront-hpa-adapter/README.md @@ -6,8 +6,6 @@ [Overview of Wavefront HPA Adapter for Kubernetes](https://github.com/wavefrontHQ/wavefront-kubernetes-adapter) - - ## TL;DR ```console diff --git a/bitnami/wavefront-kubernetes-collector/README.md b/bitnami/wavefront-kubernetes-collector/README.md index dd74ea27146c..9d3dedece674 100644 --- a/bitnami/wavefront-kubernetes-collector/README.md +++ b/bitnami/wavefront-kubernetes-collector/README.md @@ -6,8 +6,6 @@ [Overview of Wavefront](https://github.com/wavefrontHQ/wavefront-collector-for-kubernetes) - - ## TL;DR ```console diff --git a/bitnami/wavefront-prometheus-storage-adapter/README.md b/bitnami/wavefront-prometheus-storage-adapter/README.md index b79fb4a0e17c..285f21eedbb0 100644 --- a/bitnami/wavefront-prometheus-storage-adapter/README.md +++ b/bitnami/wavefront-prometheus-storage-adapter/README.md @@ -6,8 +6,6 @@ [Overview of Wavefront Prometheus Adapter](https://github.com/wavefrontHQ/prometheus-storage-adapter) - - ## TL;DR ```console diff --git a/bitnami/wavefront-proxy/README.md b/bitnami/wavefront-proxy/README.md index 910e395c5c15..7241a0302f70 100644 --- a/bitnami/wavefront-proxy/README.md +++ b/bitnami/wavefront-proxy/README.md @@ -6,8 +6,6 @@ [Overview of Wavefront Proxy](https://github.com/wavefrontHQ/wavefront-proxy) - - ## TL;DR ```console diff --git a/bitnami/zookeeper/README.md b/bitnami/zookeeper/README.md index 3d179e83fb55..07a6adf92e98 100644 --- a/bitnami/zookeeper/README.md +++ b/bitnami/zookeeper/README.md @@ -325,7 +325,7 @@ services: ### Setting up an Apache ZooKeeper ensemble -A Apache ZooKeeper (https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html) cluster can easily be setup with the Bitnami Apache ZooKeeper Docker image using the following environment variables: +An Apache ZooKeeper () cluster can easily be setup with the Bitnami Apache ZooKeeper Docker image using the following environment variables: * `ZOO_SERVERS`: Comma, space or semi-colon separated list of servers. This can be done with or without specifying the ID of the server in the ensemble. No defaults. Examples: * without Server ID - zoo1:2888:3888,zoo2:2888:3888