Merge ~athos-ribeiro/ubuntu-docker-images:update-templates-21.04-makefile into ~valentinviennot/ubuntu-docker-images:update-templates-21.04

[Athos Ribeiro]

Hi Valentin,

This MP is a proposal for adding a Makefile into the new OCI docs structure.

This also proposes a change for the build directory where the built docs artifacts should live, moving them from out* to a docs/REGISTRY/NAMESPACE structure.

Finally, while the last commit moves the files from out/* to the new structure, it also removed the files from out-lts, since I could not find the templates that generated those files.

[Athos Ribeiro (athos-ribeiro)]

Note that I do have some remaining questions over the new structure:

1 - Should we remove all the documentation bits from the individial OCI repositories in favor of the new structure? i.e., remove data?* and README.md from those repositories.

2 - How about the HACKING files? Should we still maintain those in the individual repositories?

[Sergio Durigan Junior (sergiodj)]

On Monday, September 13 2021, Athos Ribeiro wrote:

> Note that I do have some remaining questions over the new structure:
>
> 1 - Should we remove all the documentation bits from the individial OCI repositories in favor of the new structure? i.e., remove data?* and README.md from those repositories.

Yes, I think that's the way to go here. AFAIU everything will now live
in the templates.git repository.

> 2 - How about the HACKING files? Should we still maintain those in the individual repositories?

My opinion is that the HACKING files belong to the git repositories.
Right now they are also generated using templates, but maybe we can make
them generic enough that they can be static files.

Thanks,

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

[Sergio Durigan Junior (sergiodj)]

Thanks for the MP, Athos.

I think this is OK, but I'd like to hear what Valentin has to say first.

Cheers.

[Valentin Viennot (valentinviennot)]

Thanks Athos! A few changes:

In the README:
- we can get rid of all the "Getting data from images repositories" instructions, as data?* files will now live in this repository.
- also, the .devcontainer could run the steps describe in the README for us :)

For the cassandra.yaml file:
- I think we need to change the version to remove the "rc" modifier as it wouldn't be part of the image tag. I also believe the 20.04 version is not an LTS, right?
- There's a "dead" link for the Kubernetes part, "TBD". This would need the absolute link to the proper configuration files.

With these changes this works well for me!

PS: I have a commit ready to fix the 3 first bullets but I don't know what to do with it. This is what my .devcontainer/Dockerfile looks like: (feel free to commit it yourself directly)
---
# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.148.1/containers/python-3/.devcontainer/base.Dockerfile
ARG VARIANT="3"
FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}

RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
    && apt-get -y install --no-install-recommends python3-mako python3-yaml

RUN cd /usr/bin && git clone https://github.com/misterw97/RenderDown \
    && pip3 --disable-pip-version-check --no-cache-dir install -r /usr/bin/RenderDown/requirements.txt \
    && rm -rf /tmp/pip-tmp
ENV RENDERDOWN /usr/bin/RenderDown/renderdown.py

review: Needs Fixing

[Valentin Viennot (valentinviennot)]

Oh, and what I've done for the README is that I removed the instructions related to "data" files and refactored the Installation section as following:
---
## Installing

### DevContainer

This repository contains a `.devcontainer` config folder to allow isolated-environment-controlled execution with [VScode](https://code.visualstudio.com/docs/remote/containers).

The DevContainer will provide you with a working environment out of the box. **You don't need any configuration.**

### Manually

```bash
git clone https://github.com/misterw97/RenderDown
sudo apt update -y && sudo apt install -y python3-mako python3-yaml
pip3 install -r RenderDown/requirements.txt
```

[Athos Ribeiro (athos-ribeiro)]

Thanks for the reviews, Sergio and Valentin.

Valentin, I fixed the 4th bullet by adding the URL for the Cassandra k8s deployment example. Would you like to rebase your remaining changes and merge them on top of my recent changes after merging this MP or would you rather me to go ahead and add those changes here?

[Valentin Viennot (valentinviennot)]

Happy to do a rebase if that's easier

review: Approve

diff --git a/Makefile b/Makefile
 new file mode 100644
index 0000000..a179a07
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,35 @@
+RENDERDOWN ?= ../RenderDown/renderdown.py
+PYTHON ?= python3
+BUILDDIR ?= docs
+DATADIR ?= data
+
+NS_DOCKERHUB = docker.io/ubuntu
+NS_ECR = public.ecr.aws/ubuntu
+NS_ECR_LTS = public.ecr.aws/lts
+
+README_TEMPLATE_DOCKERHUB = templates/README_DOCKERHUB.md
+README_TEMPLATE_ECR = templates/README_ECR.md
+README_TEMPLATE_ECR_LTS = templates/README_ECR_LTS.md
+
+all: all-doc
+
+all-doc: clean-doc dockerhub-docs ecr-docs ecr-lts-docs
+
+dockerhub-docs:
+	mkdir -p $(BUILDDIR)/$(NS_DOCKERHUB)
+	$(PYTHON) $(RENDERDOWN) $(README_TEMPLATE_DOCKERHUB) --outdir $(BUILDDIR)/$(NS_DOCKERHUB) --data $(DATADIR)
+
+ecr-docs:
+	mkdir -p $(BUILDDIR)/$(NS_ECR)
+	$(PYTHON) $(RENDERDOWN) $(README_TEMPLATE_ECR) --outdir $(BUILDDIR)/$(NS_ECR) --data $(DATADIR)
+
+ecr-lts-docs:
+	mkdir -p $(BUILDDIR)/$(NS_ECR_LTS)
+	$(PYTHON) $(RENDERDOWN) $(README_TEMPLATE_ECR_LTS) --outdir $(BUILDDIR)/$(NS_ECR_LTS) --data $(DATADIR)
+
+clean: clean-doc
+
+clean-doc:
+	rm -rf $(BUILDDIR)
+
+.PHONY: clean clean-doc all all-doc dockerhub-docs ecr-docs ecr-lts-docs
diff --git a/README.md b/README.md
index d9b66cb..f0402b2 100644
--- a/README.md
+++ b/README.md
@@ -35,8 +35,19 @@ python3 ./RenderDown/renderdown.py templates/README_DOCKERHUB.md --outdir out --
 
 #### Useful commands
 
+Create README files for all resigtries and namespaces:
+
+```bash
+make
+```
+
+Create a README file for a specific registry/namespace combination:
+
 ```bash
-python3 ./RenderDown/renderdown.py templates/README_DOCKERHUB.md --outdir ./out/DockerHub/Ubuntu --data ./data
-python3 ./RenderDown/renderdown.py templates/README_ECR.md --outdir ./out/ECR/Ubuntu --data ./data
-python3 ./RenderDown/renderdown.py templates/README_ECR_LTS.md --outdir ./out/ECR/LTS --data ./data
+make dockerhub-docs
+make ecr-docs
+make ecr-lts-docs
 ```
+
+The documentation will be available under `docs`, respecting the image
+registry/namespace format.
diff --git a/data/cassandra.yaml b/data/cassandra.yaml
index bfdf4f7..7e640cb 100644
--- a/data/cassandra.yaml
+++ b/data/cassandra.yaml
@@ -61,5 +61,5 @@ debug:
   - nothing
 microk8s:
   deploy:
-    link: TBD
+    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml
     access: You can now access the cassandra server on port 9042 (e.g., cqlsh localhost 9042)
diff --git a/out/DockerHub/Ubuntu/apache2.md b/docs/docker.io/ubuntu/apache2.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/apache2.md
 rename to docs/docker.io/ubuntu/apache2.md
diff --git a/out/DockerHub/Ubuntu/cassandra.md b/docs/docker.io/ubuntu/cassandra.md
 similarity index 96%
 rename from out/DockerHub/Ubuntu/cassandra.md
 rename to docs/docker.io/ubuntu/cassandra.md
index e71ed9e..7ae1de4 100644
--- a/out/DockerHub/Ubuntu/cassandra.md
+++ b/docs/docker.io/ubuntu/cassandra.md
@@ -73,7 +73,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](TBD) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cassandra:4.0-rc1-21.04_beta`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `ubuntu/cassandra:4.0-rc1-21.04_beta`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/out/DockerHub/Ubuntu/cortex.md b/docs/docker.io/ubuntu/cortex.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/cortex.md
 rename to docs/docker.io/ubuntu/cortex.md
diff --git a/out/DockerHub/Ubuntu/grafana.md b/docs/docker.io/ubuntu/grafana.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/grafana.md
 rename to docs/docker.io/ubuntu/grafana.md
diff --git a/out/DockerHub/Ubuntu/memcached.md b/docs/docker.io/ubuntu/memcached.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/memcached.md
 rename to docs/docker.io/ubuntu/memcached.md
diff --git a/out/DockerHub/Ubuntu/mysql.md b/docs/docker.io/ubuntu/mysql.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/mysql.md
 rename to docs/docker.io/ubuntu/mysql.md
diff --git a/out/DockerHub/Ubuntu/nginx.md b/docs/docker.io/ubuntu/nginx.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/nginx.md
 rename to docs/docker.io/ubuntu/nginx.md
diff --git a/out/DockerHub/Ubuntu/postgres.md b/docs/docker.io/ubuntu/postgres.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/postgres.md
 rename to docs/docker.io/ubuntu/postgres.md
diff --git a/out/DockerHub/Ubuntu/prometheus-alertmanager.md b/docs/docker.io/ubuntu/prometheus-alertmanager.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/prometheus-alertmanager.md
 rename to docs/docker.io/ubuntu/prometheus-alertmanager.md
diff --git a/out/DockerHub/Ubuntu/prometheus.md b/docs/docker.io/ubuntu/prometheus.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/prometheus.md
 rename to docs/docker.io/ubuntu/prometheus.md
diff --git a/out/DockerHub/Ubuntu/redis.md b/docs/docker.io/ubuntu/redis.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/redis.md
 rename to docs/docker.io/ubuntu/redis.md
diff --git a/out/DockerHub/Ubuntu/telegraf.md b/docs/docker.io/ubuntu/telegraf.md
 similarity index 100%
 rename from out/DockerHub/Ubuntu/telegraf.md
 rename to docs/docker.io/ubuntu/telegraf.md
diff --git a/out/ECR/LTS/apache2.md b/docs/public.ecr.aws/lts/apache2.md
 similarity index 100%
 rename from out/ECR/LTS/apache2.md
 rename to docs/public.ecr.aws/lts/apache2.md
diff --git a/out/ECR/LTS/cassandra.md b/docs/public.ecr.aws/lts/cassandra.md
 similarity index 96%
 rename from out/ECR/LTS/cassandra.md
 rename to docs/public.ecr.aws/lts/cassandra.md
index f44bd91..48ac796 100644
--- a/out/ECR/LTS/cassandra.md
+++ b/docs/public.ecr.aws/lts/cassandra.md
@@ -74,7 +74,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](TBD) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cassandra:4.0-rc1-20.04_beta`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/lts/cassandra:4.0-rc1-20.04_beta`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/out/ECR/LTS/cortex.md b/docs/public.ecr.aws/lts/cortex.md
 similarity index 100%
 rename from out/ECR/LTS/cortex.md
 rename to docs/public.ecr.aws/lts/cortex.md
diff --git a/out/ECR/LTS/grafana.md b/docs/public.ecr.aws/lts/grafana.md
 similarity index 100%
 rename from out/ECR/LTS/grafana.md
 rename to docs/public.ecr.aws/lts/grafana.md
diff --git a/out/ECR/LTS/memcached.md b/docs/public.ecr.aws/lts/memcached.md
 similarity index 100%
 rename from out/ECR/LTS/memcached.md
 rename to docs/public.ecr.aws/lts/memcached.md
diff --git a/out/ECR/LTS/mysql.md b/docs/public.ecr.aws/lts/mysql.md
 similarity index 100%
 rename from out/ECR/LTS/mysql.md
 rename to docs/public.ecr.aws/lts/mysql.md
diff --git a/out/ECR/LTS/nginx.md b/docs/public.ecr.aws/lts/nginx.md
 similarity index 100%
 rename from out/ECR/LTS/nginx.md
 rename to docs/public.ecr.aws/lts/nginx.md
diff --git a/out/ECR/LTS/postgres.md b/docs/public.ecr.aws/lts/postgres.md
 similarity index 100%
 rename from out/ECR/LTS/postgres.md
 rename to docs/public.ecr.aws/lts/postgres.md
diff --git a/out/ECR/LTS/prometheus-alertmanager.md b/docs/public.ecr.aws/lts/prometheus-alertmanager.md
 similarity index 100%
 rename from out/ECR/LTS/prometheus-alertmanager.md
 rename to docs/public.ecr.aws/lts/prometheus-alertmanager.md
diff --git a/out/ECR/LTS/prometheus.md b/docs/public.ecr.aws/lts/prometheus.md
 similarity index 100%
 rename from out/ECR/LTS/prometheus.md
 rename to docs/public.ecr.aws/lts/prometheus.md
diff --git a/out/ECR/LTS/redis.md b/docs/public.ecr.aws/lts/redis.md
 similarity index 100%
 rename from out/ECR/LTS/redis.md
 rename to docs/public.ecr.aws/lts/redis.md
diff --git a/out/ECR/LTS/telegraf.md b/docs/public.ecr.aws/lts/telegraf.md
 similarity index 100%
 rename from out/ECR/LTS/telegraf.md
 rename to docs/public.ecr.aws/lts/telegraf.md
diff --git a/out/ECR/Ubuntu/apache2.md b/docs/public.ecr.aws/ubuntu/apache2.md
 similarity index 100%
 rename from out/ECR/Ubuntu/apache2.md
 rename to docs/public.ecr.aws/ubuntu/apache2.md
diff --git a/out/ECR/Ubuntu/cassandra.md b/docs/public.ecr.aws/ubuntu/cassandra.md
 similarity index 96%
 rename from out/ECR/Ubuntu/cassandra.md
 rename to docs/public.ecr.aws/ubuntu/cassandra.md
index fd7aef9..e4ec4d4 100644
--- a/out/ECR/Ubuntu/cassandra.md
+++ b/docs/public.ecr.aws/ubuntu/cassandra.md
@@ -76,7 +76,7 @@ docker exec -it cassandra-container /bin/bash
 Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
 
 Download
-[cassandra-deployment.yml](TBD) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cassandra:4.0-rc1-20.04_beta`), then:
+[cassandra-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cassandra/plain/examples/cassandra-deployment.yml) and set `containers.cassandra.image` in `cassandra-deployment.yml` to your chosen channel tag (e.g. `public.ecr.aws/ubuntu/cassandra:4.0-rc1-20.04_beta`), then:
 
 ```sh
 kubectl apply -f cassandra-deployment.yml
diff --git a/out/ECR/Ubuntu/cortex.md b/docs/public.ecr.aws/ubuntu/cortex.md
 similarity index 100%
 rename from out/ECR/Ubuntu/cortex.md
 rename to docs/public.ecr.aws/ubuntu/cortex.md
diff --git a/out/ECR/Ubuntu/grafana.md b/docs/public.ecr.aws/ubuntu/grafana.md
 similarity index 100%
 rename from out/ECR/Ubuntu/grafana.md
 rename to docs/public.ecr.aws/ubuntu/grafana.md
diff --git a/out/ECR/Ubuntu/memcached.md b/docs/public.ecr.aws/ubuntu/memcached.md
 similarity index 100%
 rename from out/ECR/Ubuntu/memcached.md
 rename to docs/public.ecr.aws/ubuntu/memcached.md
diff --git a/out/ECR/Ubuntu/mysql.md b/docs/public.ecr.aws/ubuntu/mysql.md
 similarity index 100%
 rename from out/ECR/Ubuntu/mysql.md
 rename to docs/public.ecr.aws/ubuntu/mysql.md
diff --git a/out/ECR/Ubuntu/nginx.md b/docs/public.ecr.aws/ubuntu/nginx.md
 similarity index 100%
 rename from out/ECR/Ubuntu/nginx.md
 rename to docs/public.ecr.aws/ubuntu/nginx.md
diff --git a/out/ECR/Ubuntu/postgres.md b/docs/public.ecr.aws/ubuntu/postgres.md
 similarity index 100%
 rename from out/ECR/Ubuntu/postgres.md
 rename to docs/public.ecr.aws/ubuntu/postgres.md
diff --git a/out/ECR/Ubuntu/prometheus-alertmanager.md b/docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md
 similarity index 100%
 rename from out/ECR/Ubuntu/prometheus-alertmanager.md
 rename to docs/public.ecr.aws/ubuntu/prometheus-alertmanager.md
diff --git a/out/ECR/Ubuntu/prometheus.md b/docs/public.ecr.aws/ubuntu/prometheus.md
 similarity index 100%
 rename from out/ECR/Ubuntu/prometheus.md
 rename to docs/public.ecr.aws/ubuntu/prometheus.md
diff --git a/out/ECR/Ubuntu/redis.md b/docs/public.ecr.aws/ubuntu/redis.md
 similarity index 100%
 rename from out/ECR/Ubuntu/redis.md
 rename to docs/public.ecr.aws/ubuntu/redis.md
diff --git a/out/ECR/Ubuntu/telegraf.md b/docs/public.ecr.aws/ubuntu/telegraf.md
 similarity index 100%
 rename from out/ECR/Ubuntu/telegraf.md
 rename to docs/public.ecr.aws/ubuntu/telegraf.md
diff --git a/out-lts/apache2.md b/out-lts/apache2.md
 deleted file mode 100644
index 743c3b2..0000000
--- a/out-lts/apache2.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# Apache2 LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Apache2
-
-The Apache HTTP Server Project's goal is to build a secure, efficient and extensible HTTP server as standards-compliant open source software. The result has long been the number one web server on the Internet. Read more on the [apache2 website](https://httpd.apache.org/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/apache2`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/apache2`.
-
-_Tags in italics are not available in lts/apache2 but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| **`2.4-20.04_beta`**    | - | - | Apache2 2.4.41 | `amd64`, `arm64`, `ppc64el`, `s390x` |
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name apache2-container -e TZ=UTC -p 8080:80 lts/apache2:2.4-20.04_beta
-```
-Access your Apache2 server at `http://localhost:8080`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 8080:80` | Expose Apache2 on `localhost:8080`. |
-| `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
-| `-v /path/to/apache2.conf:/etc/apache2/apache2.conf` | Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f apache2-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it apache2-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[apache2.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html) and
-[apache2-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml) and set `containers.apache2.image` in `apache2-deployment.yml` to your chosen channel tag (e.g. `lts/apache2:2.4-20.04_beta`), then:
-
-```sh
-kubectl create configmap apache2-config --from-file=apache2=apache2.conf --from-file=apache2-site=index.html
-kubectl apply -f apache2-deployment.yml
-```
-
-You will now be able to connect to the apache2 server on `http://localhost:30080`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`apache2: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/apache2:<tag>
-```
-
diff --git a/out-lts/cortex.md b/out-lts/cortex.md
 deleted file mode 100644
index ae779d0..0000000
--- a/out-lts/cortex.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Cortex LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Cortex
-
-Cortex provides horizontally scalable, highly available, multi-tenant, long term storage for Prometheus.
-
-* Horizontally scalable: Cortex can run across multiple machines in a cluster, exceeding the throughput and storage of a single machine. This enables you to send the metrics from multiple Prometheus servers to a single Cortex cluster and run "globally aggregated" queries across all data in a single place.
-* Highly available: When run in a cluster, Cortex can replicate data between machines. This allows you to survive machine failure without gaps in your graphs.
-* Multi-tenant: Cortex can isolate data and queries from multiple different independent Prometheus sources in a single cluster, allowing untrusted parties to share the same cluster.
-* Long term storage: Cortex supports Amazon DynamoDB, Google Bigtable, Cassandra, S3, GCS and Microsoft Azure for long term storage of metric data. This allows you to durably store data for longer than the lifetime of any single machine, and use this data for long term capacity planning.
-
-Read more on the [Cortex website](https://cortexmetrics.io/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/cortex`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/cortex`.
-
-_Tags in italics are not available in lts/cortex but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name cortex-container -e TZ=UTC -p 32709:9009 lts/cortex:1.4-20.04_beta
-```
-Access your Cortex server at `http://localhost:32709`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 32709:9009` | Expose Cortex on `localhost:32709`. |
-| `-v /my/local/cortex.yaml:/etc/cortex/cortex.yaml` | Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f cortex-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it cortex-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[cortex.yaml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml) and
-[cortex-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml) and set `containers.cortex.image` in `cortex-deployment.yml` to your chosen channel tag (e.g. `lts/cortex:1.4-20.04_beta`), then:
-
-```sh
-kubectl create configmap cortex-config --from-file=main-config=cortex.yaml
-kubectl apply -f cortex-deployment.yml
-```
-
-You will now be able to connect to the Cortex server on `localhost:32709`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`cortex: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/cortex:<tag>
-```
-
diff --git a/out-lts/grafana.md b/out-lts/grafana.md
 deleted file mode 100644
index af4cee1..0000000
--- a/out-lts/grafana.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Grafana LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Grafana
-
-Grafana is a feature rich metrics dashboard and graph editor for Cloudwatch, Elasticsearch, Graphite, InfluxDB, OpenTSB, Prometheus, and Hosted Metrics.  Read more on the [Grafana website](https://grafana.com/docs/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/grafana`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/grafana`.
-
-_Tags in italics are not available in lts/grafana but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name grafana-container -e TZ=UTC -p 30000:3000 lts/grafana:7.2-20.04_beta
-```
-Access your Grafana server at `localhost:30000`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 30000:3000` | Expose Grafana on `localhost:30000`. |
-| `-v /path/to/grafana/provisioning/files/:/etc/grafana/provisioning/` | Pass a directory with files to provision a Grafana `datasource` and `dashboard` (see [documentation](https://grafana.com/docs/grafana/latest/administration/provisioning/)). |
-| `-v /path/to/persisted/data:/var/lib/grafana` | Persist data with a voulme instead of initializing a new database for each newly launched container. |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f grafana-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it grafana-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[datasource.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml), [dashboard.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml), [system-stats-dashboard.json](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json) and
-[grafana-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml) and set `containers.grafana.image` in `grafana-deployment.yml` to your chosen channel tag (e.g. `lts/grafana:7.2-20.04_beta`), then:
-
-```sh
-kubectl create configmap grafana-config --from-file=grafana-datasource=datasource.yml --from-file=grafana-dashboard-definition=dashboard.yml --from-file=grafana-dashboard=system-stats-dashboard.json
-kubectl apply -f grafana-deployment.yml
-```
-
-You will now be able to connect to the Grafana on `http://localhost:30000`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`grafana: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/grafana:<tag>
-```
-
diff --git a/out-lts/memcached.md b/out-lts/memcached.md
 deleted file mode 100644
index c33827e..0000000
--- a/out-lts/memcached.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Memcached LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Memcached
-
-Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering. It is a short-term memory for applications. Memcached allows to take memory from parts of a system where you have more than you need and make it accessible to areas where you have less than you need. Read more on the [memcached website](https://memcached.org/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/memcached`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/memcached`.
-
-_Tags in italics are not available in lts/memcached but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| **`1.5-20.04_beta`** &nbsp;&nbsp; | - | - | Memcached 1.5.22 | `amd64`, `arm64`, `ppc64el`, `s390x` |
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name memcached-container -e TZ=UTC  lts/memcached:1.5-20.04_beta
-```
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-e MEMCACHED_CACHE_SIZE=64MB` | Determines the size of the cache. |
-| `-e MEMCACHED_MAX_CONNECTIONS=1024` | Determines the maximum number of concurrent connections. |
-| `-e MEMCACHED_THREADS=4` | Determines the number of threads to process requests. |
-| `-e MEMCACHED_PASSWORD` | Define the password for the `root` user if another username is provided. By default the authentication is disabled but if this option is passed it becomes enabled. |
-| `-e MEMCACHED_USERNAME` | Define a new user. If this option is passed a password is needed to authenticate the new user. |
-| `-p 11211` | Memcached is exposed inside the container on port `11211`. |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f memcached-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it memcached-container /bin/bash
-```
-
-<details>
-<summary>You can access the Memcached instance with telnet from another container (click to expand).</summary>
-
-```sh
-# Create a dedicated network
-$ docker network create memcached-network
-# Connect the main container to it
-$ docker network connect memcached-network memcached-container
-# Run an interactive container with the latest Ubuntu
-$ docker run -it --rm --name telnet --network memcached-network ubuntu bash
-# Install the telnet cli from within the container
-> apt update && apt install telnet -y
-# Connect to the memcached instance using telnet
-> telnet memcached-container 11211
-Trying 172.30.0.2...
-Connected to memcached.
-Escape character is '^]'.
-```
-From there you can run `memcached` commands, as documented in [their wiki](https://github.com/memcached/memcached/wiki/Commands).
-
-</details>
-
-```sh
-$ telnet memcached-container 11211
-```
-
-There are cases where one might want to pass some memcached command line flags that are not configurable via environment variables.
-In this case you can append the flags themselves or a shell script to the run command.
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[memcached-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml) and set `containers.memcached.image` in `memcached-deployment.yml` to your chosen channel tag (e.g. `lts/memcached:1.5-20.04_beta`), then:
-
-```sh
-kubectl apply -f memcached-deployment.yml
-```
-
-Memcached will be listening on port `31211` in your host.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`memcached: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/memcached:<tag>
-```
-
diff --git a/out-lts/mysql.md b/out-lts/mysql.md
 deleted file mode 100644
index 6239da7..0000000
--- a/out-lts/mysql.md
+++ /dev/null
@@ -1,116 +0,0 @@
-# MySQL LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About MySQL
-
-MySQL is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of MySQL are speed, robustness and ease of use. Read more on the [MySQL website](https://dev.mysql.com/doc/refman/8.0/en/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/mysql`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/mysql`.
-
-_Tags in italics are not available in lts/mysql but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| **`8.0-20.04_beta`** &nbsp;&nbsp; | - | - | MySQL 8.0.22 | `amd64`, `arm64`, `s390x` |
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name mysql-container -e TZ=UTC -p 30306:3306 -e MYSQL_ROOT_PASSWORD=My:S3cr3t/ lts/mysql:8.0-20.04_beta
-```
-Access your MySQL server at `localhost:30306`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-e MYSQL_ROOT_PASSWORD=secret_for_root` | Set the password for the `root` user. This option is **mandatory** and **must not be empty**. |
-| `-e MYSQL_PASSWORD=secret` | Set the password for the `MYSQL_USER` user. |
-| `-e MYSQL_USER=john` | Create a new user with superuser privileges. This is used in conjunction with `MYSQL_PASSWORD`. |
-| `-e MYSQL_DATABASE=db_test` | Set the name of the default database. |
-| `-e MYSQL_ALLOW_EMPTY_PASSWORD=yes` | Set up a blank password for the `root` user. **This is not recommended to be used in production, make sure you know what you are doing**. |
-| `-e MYSQL_RANDOM_ROOT_PASSWORD=yes` | Generate a random initial password for the `root` user using `pwgen`. It will be printed in the logs, search for `GENERATED ROOT PASSWORD`. |
-| `-e MYSQL_ONETIME_PASSWORD=yes` | Set `root` user as experide once initialization is complete, forcing a password change on first login. |
-| `-e MYSQL_INITSB_SKIP_TZINFO=yes` | Timezone data is automatically loaded via entrypoint script, set this variable to any non-empty value to disable it. |
-| `-p 30306:3306` | Expose MySQL server on `localhost:30306`. |
-| `-v /path/to/data:/var/lib/mysql` | Persist data instead of initializing a new database every time you launch a new container. |
-| `-v /path/to/config/files/:/etc/mysql/mysql.conf.d/` | Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my.cnf)). |
-
-#### Initialization Scripts
-
-One can also add initialization scripts to their containers. This includes `*.sql`, `.sql.gz`, and `*.sh` scripts, and you just need to put them inside the  `/docker-entrypoint-initdb.d` directory inside the container. After MySQL initialization is done and the default database and user are created, the scripts are executed in the following order:
-
-* Run any `*.sql` files in alphabetically order. By default the target database is specified via `MYSQL_DATABASE`.
-* Run any executable `*.sh` scripts in alphabetically order.
-* Source any non-executable `*.sh` scripts in alphabetically order.
-
-All of this is done before the MySQL service is started. Keep in mind if your database directory is not empty (contains pre-existing database) they will be left untouched.
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f mysql-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it mysql-container /bin/bash
-```
-
-This image also includes the `mysql` client for interactive container use:
-
-```sh
-$ docker network create mysql-network
-$ docker network connect mysql-network mysql-container
-$ docker run -it --rm --network mysql-network lts/mysql:8.0-20.04_beta mysql -hmysql-container -uroot -p
-```
-The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged in and can enjoy your new instance.
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[my-custom.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf) and
-[mysql-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml) and set `containers.mysql.image` in `mysql-deployment.yml` to your chosen channel tag (e.g. `lts/mysql:8.0-20.04_beta`), then:
-
-```sh
-kubectl create configmap mysql-config --from-file=main-config=my-custom.cnf
-kubectl apply -f mysql-deployment.yml
-```
-
-You will now be able to connect to the MySQL server on `localhost:30306`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`mysql: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/mysql:<tag>
-```
-
diff --git a/out-lts/nginx.md b/out-lts/nginx.md
 deleted file mode 100644
index d837f3c..0000000
--- a/out-lts/nginx.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Nginx LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Nginx
-
-Nginx ("engine X") is a high-performance web and reverse proxy server created by Igor Sysoev. It can be used both as a standalone web server and as a proxy to reduce the load on back-end HTTP or mail servers. Read more on the [nginx website](https://www.nginx.com/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/nginx`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/nginx`.
-
-_Tags in italics are not available in lts/nginx but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| **`1.18-20.04_beta`** &nbsp;&nbsp; | - | - | Nginx 1.18.0 | `amd64`, `arm64`, `ppc64el`, `s390x` |
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name nginx-container -e TZ=UTC -p 8080:80 lts/nginx:1.18-20.04_beta
-```
-Access your Nginx server at `http://localhost:8080`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 8080:80` | Expose Nginx on `localhost:8080`. |
-| `-v /local/path/to/website:/var/www/html` | Mount and serve a local website. |
-| `-v /path/to/conf.template:/etc/nginx/templates/conf.template` | Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`). |
-| `-v /path/to/nginx.conf:/etc/nginx/nginx.conf` | Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f nginx-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it nginx-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[nginx.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf), [index.html](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html) and
-[nginx-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml) and set `containers.nginx.image` in `nginx-deployment.yml` to your chosen channel tag (e.g. `lts/nginx:1.18-20.04_beta`), then:
-
-```sh
-kubectl create configmap nginx-config --from-file=nginx=nginx.conf --from-file=nginx-site=index.html
-kubectl apply -f nginx-deployment.yml
-```
-
-You will now be able to connect to the nginx server on `http://localhost:31080`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`nginx: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/nginx:<tag>
-```
-
diff --git a/out-lts/postgres.md b/out-lts/postgres.md
 deleted file mode 100644
index 49c284b..0000000
--- a/out-lts/postgres.md
+++ /dev/null
@@ -1,115 +0,0 @@
-# Postgres LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Postgres
-
-PostgreSQL is a powerful, open source object-relational database system. It is fully ACID compliant, has full support for foreign keys, joins, views, triggers, and stored procedures (in multiple languages). It includes most SQL:2008 data types, including INTEGER, NUMERIC, BOOLEAN, CHAR, VARCHAR, DATE, INTERVAL, and TIMESTAMP. It also supports storage of binary large objects, including pictures, sounds, or video. It has native programming interfaces for C/C++, Java, .Net, Perl, Python, Ruby, Tcl, ODBC, among others, and exceptional documentation. Read more on the [PostgreSQL website](https://www.postgresql.org/docs/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/postgres`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/postgres`.
-
-_Tags in italics are not available in lts/postgres but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| **`12.4-20.04_beta`** &nbsp;&nbsp; | - | - | Postgres 12.4 | `amd64`, `arm64`, `s390x` |
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name postgres-container -e TZ=UTC -p 30432:5432 -e POSTGRES_PASSWORD=My:s3Cr3t/ lts/postgres:12.4-20.04_beta
-```
-Access your PostgreSQL server at `localhost:30432`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-e POSTGRES_PASSWORD=secret` | Set the password for the superuser which is `postgres` by default. Bear in mind that to connect to the database in the same host the password is not needed but to access it via an external host (for instance another container) the password is needed. This option is **mandatory** and **must not be empty**. |
-| `-e POSTGRES_USER=john` | Create a new user with superuser privileges. This is used in conjunction with `POSTGRES_PASSWORD`. |
-| `-e POSTGRES_DB=db_test` | Set the name of the default database. |
-| `-e POSTGRES_INITDB_ARGS="--data-checksums"` | Pass arguments to the `postgres initdb` call. |
-| `-e POSTGRES_INITDB_WALDIR=/path/to/location` | Set the location of the Postgres transaction log. By default it is stored in a subdirectory of the main Postgres data folder (`PGDATA`). |
-| `-e POSTGRES_HOST_AUTH_METHOD=trust` | Set the `auth-method` for `host` connections for `all` databases, `all` users, and `all` addresses. The following will be added to the `pg_hba.conf` if this option is passed: `host all all all $POSTGRES_HOST_AUTH_METHOD`. |
-| `-e PGDATA=/path/to/location` | Set the location of the database files. The default is `/var/lib/postgresql/data`. |
-| `-p 30432:5432` | Expose Postgres on `localhost:30432`. |
-| `-v /path/to/postgresql.conf:/etc/postgresql/postgresql.conf` | Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf)). |
-| `-v /path/to/persisted/data:/var/lib/postgresql/data` | Persist data instead of initializing a new database every time you launch a new container. |
-
-#### Initialization Scripts
-
-One can also add initialization scripts to their containers. This includes `*.sql`, `.sql.gz`, and `*.sh` scripts, and you just need to put them inside the  `/docker-entrypoint-initdb.d` directory inside the container. After Postgres initialization is done and the default database and user are created, the scripts are executed in the following order:
-
-* Run any `*.sql` files in alphabetically order. It will be executed with `POSTGRES_USER`.
-* Run any executable `*.sh` scripts in alphabetically order.
-* Source any non-executable `*.sh` scripts in alphabetically order.
-
-All of this is done before the Postgres service is started. Keep in mind if your `PGDATA` directory is not empty (contains pre-existing database) they will be left untouched.
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f postgres-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it postgres-container /bin/bash
-```
-
-This image also includes the `psql` client for interactive container use:
-
-```sh
-$ docker network create postgres-network
-$ docker network connect postgres-network postgres-container
-$ docker run -it --rm --network postgres-network lts/postgres:12.4-20.04_beta psql -h postgres-container -U postgres
-```
-The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged in and can enjoy your new instance.
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[postgresql.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf) and
-[postgres-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml) and set `containers.postgres.image` in `postgres-deployment.yml` to your chosen channel tag (e.g. `lts/postgres:12.4-20.04_beta`), then:
-
-```sh
-kubectl create configmap postgres-config --from-file=main-config=postgresql.conf
-kubectl apply -f postgres-deployment.yml
-```
-
-You will now be able to connect to the Postgres server on `localhost:30306`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`postgres: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/postgres:<tag>
-```
-
diff --git a/out-lts/prometheus-alertmanager.md b/out-lts/prometheus-alertmanager.md
 deleted file mode 100644
index 146a4b8..0000000
--- a/out-lts/prometheus-alertmanager.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Prometheus Alertmanager LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Prometheus Alertmanager
-
-The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts. Read more on the [Prometheus Alertmanager website](https://prometheus.io/docs/alerting/latest/alertmanager/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/prometheus-alertmanager`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/prometheus-alertmanager`.
-
-_Tags in italics are not available in lts/prometheus-alertmanager but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name prometheus-alertmanager-container -e TZ=UTC -p 30093:9093 lts/prometheus-alertmanager:0.21-20.04_beta
-```
-Access your Prometheus Alertmanager server at `localhost:30093`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 30093:9093` | Expose Prometheus Alertmanager on `localhost:30093`. |
-| `-v /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml` | Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/config/alertmanager.yml)). |
-| `-v /path/to/persisted/data:/alertmanager` | Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container. |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f prometheus-alertmanager-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it prometheus-alertmanager-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[alertmanager.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/config/alertmanager.yml) and
-[prometheus-alertmanager-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/alertmanager-deployment.yml) and set `containers.prometheus-alertmanager.image` in `prometheus-alertmanager-deployment.yml` to your chosen channel tag (e.g. `lts/prometheus-alertmanager:0.21-20.04_beta`), then:
-
-```sh
-kubectl create configmap prometheus-alertmanager-config --from-file=alertmanager=alertmanager.yml
-kubectl apply -f prometheus-alertmanager-deployment.yml
-```
-
-You will now be able to connect to the Prometheus Alertmanager server on `localhost:30093`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`prometheus-alertmanager: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/prometheus-alertmanager:<tag>
-```
-
diff --git a/out-lts/prometheus.md b/out-lts/prometheus.md
 deleted file mode 100644
index 3c4066d..0000000
--- a/out-lts/prometheus.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Prometheus LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Prometheus
-
-Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. Read more on the [Prometheus website](https://prometheus.io/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/prometheus`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/prometheus`.
-
-_Tags in italics are not available in lts/prometheus but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name prometheus-container -e TZ=UTC -p 30090:9090 lts/prometheus:2.20-20.04_beta
-```
-Access your Prometheus server at `localhost:30090`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 30090:9090` | Expose Prometheus server on `localhost:30090`. |
-| `-v /path/to/prometheus.yml:/etc/prometheus/prometheus.yml` | Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/prometheus.yml)). |
-| `-v /path/to/alerts.yml:/etc/prometheus/alerts.yml` | Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/alerts.yml)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f prometheus-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it prometheus-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[prometheus.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/prometheus.yml), [alerts.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/alerts.yml) and
-[prometheus-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/prometheus-deployment.yml) and set `containers.prometheus.image` in `prometheus-deployment.yml` to your chosen channel tag (e.g. `lts/prometheus:2.20-20.04_beta`), then:
-
-```sh
-kubectl create configmap prometheus-config --from-file=prometheus=prometheus.yml --from-file=prometheus-alerts=alerts.yml
-kubectl apply -f prometheus-deployment.yml
-```
-
-You will now be able to connect to the Prometheus on `http://localhost:30090`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`prometheus: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/prometheus:<tag>
-```
-
diff --git a/out-lts/redis.md b/out-lts/redis.md
 deleted file mode 100644
index b4b7fda..0000000
--- a/out-lts/redis.md
+++ /dev/null
@@ -1,109 +0,0 @@
-# Redis LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Redis
-
-Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker.  It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes with radius queries and streams.  Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability via Redis Sentinel and automatic partitioning with Redis Cluster.  Read more on the [Redis website](https://redis.io/topics/introduction).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/redis`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/redis`.
-
-_Tags in italics are not available in lts/redis but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name redis-container -e TZ=UTC -p 30073:6379 -e REDIS_PASSWORD=mypassword lts/redis:5.0-20.04_beta
-```
-Access your Redis server at `localhost:30073`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-e ALLOW_EMPTY_PASSWORD` | Set to `yes` to allow connections to `redis-server` without a password.  **This setting is not recommended in production environments**. |
-| `-e REDIS_PASSWORD` | Set the desired password to be used. |
-| `-e REDIS_RANDOM_PASSWORD` | Set this variable to `1` if you would like the entrypoint script to generate a random password for you.  You will be able to see the generated password in the logs (`docker logs`). |
-| `-e REDIS_ALLOW_REMOTE_CONNECTIONS=yes` | Set to `no` to disallow remote connections to `redis-server` (i.e., make `redis-server` listen to `127.0.0.1` only). |
-| `-e REDIS_EXTRA_FLAGS` | Specify extra flags to be passed to `redis-server` when initializing it. |
-| `-p 30073:6379` | Expose redis on `localhost:30073`. |
-| `-v /path/to/redis.conf:/etc/redis/redis.conf` | Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f redis-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it redis-container /bin/bash
-```
-
-This image also includes the `redis-cli` client for interactive container use:
-
-```sh
-$ docker network create redis-network
-$ docker network connect redis-network redis-container
-$ docker run -it --rm --network redis-network lts/redis:5.0-20.04_beta redis-cli -h redis-container
-```
-Now you can:
-```
-redis:6379> AUTH mypassword
-OK
-redis:6379> PING
-PONG
-redis:6379>
-
-```
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[redis.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf) and
-[redis-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml) and set `containers.redis.image` in `redis-deployment.yml` to your chosen channel tag (e.g. `lts/redis:5.0-20.04_beta`), then:
-
-```sh
-kubectl create configmap redis-config --from-file=redis=redis.conf
-kubectl apply -f redis-deployment.yml
-```
-
-You will now be able to connect to the Redis server on `localhost:30073`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`redis: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/redis:<tag>
-```
-
diff --git a/out-lts/telegraf.md b/out-lts/telegraf.md
 deleted file mode 100644
index 778a1e4..0000000
--- a/out-lts/telegraf.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Telegraf LTS Docker Image
-
-## LTS Docker Image Portfolio
-The [LTS Docker Image Portfolio](https://ubuntu.com/security/docker-images) are consistent, compliant, minimal and secure images with Extended Security Maintenance (ESM) commitments from Canonical. This repository is exempted from per-user rate limits.
-
-
-## About Telegraf
-
-Telegraf is an agent for collecting, processing, aggregating, and writing metrics. Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics. Read more on the [Telegraf website](https://www.influxdata.com/time-series-platform/telegraf/).
-
-
-## Tags and Architectures
-![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17)
-Up to 5 years free security maintenance `from lts/telegraf`.
-
-![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17)
-Up to 10 years customer security maintenance `from store/canonical/telegraf`.
-
-_Tags in italics are not available in lts/telegraf but are shown here for completeness._
-
-| Channel Tag | ![LTS](https://assets.ubuntu.com/v1/0a5ff561-LTS%402x.png?h=17) until | ![ESM](https://assets.ubuntu.com/v1/572f3fbd-ESM%402x.png?h=17) until | Currently | Architectures |
-|---|---|---|---|---|
-| _`track_risk`_ |
-
-Channel tag shows the most stable channel for that track ordered `stable`, `candidate`, `beta`, `edge`. More risky channels are always implicitly available. So if `beta` is listed, you can also pull `edge`. If `candidate` is listed, you can pull beta and edge. When `stable` is listed, all four are available. Images are guaranteed to progress through the sequence `edge`, `beta`, `candidate` before `stable`.
-
-## Usage
-
-If your usage includes redistribution, please [contact Canonical](https://ubuntu.com/security/docker-images#get-in-touch).
-
-Launch this image locally:
-
-```sh
-docker run -d --name telegraf-container -e TZ=UTC -p 30273:9273 lts/telegraf:1.15-20.04_beta
-```
-Access your Telegraf server at `localhost:30273`.
-
-#### Parameters
-
-| Parameter | Description |
-|---|---|
-| `-e TZ=UTC` | Timezone. |
-| `-p 30273:9273` | Expose Telegraf on `localhost:30273`. |
-| `-v /path/to/telegraf.conf:/etc/telegraf/telegraf.conf` | Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf)). |
-
-
-#### Testing/Debugging
-
-To debug the container:
-
-```sh
-docker logs -f telegraf-container
-```
-
-To get an interactive shell:
-
-```sh
-docker exec -it telegraf-container /bin/bash
-```
-
-
-## Deploy with Kubernetes
-
-Works with any Kubernetes; if you don't have one, we recommend you [install MicroK8s](https://microk8s.io/) and `microk8s.enable dns storage` then `snap alias microk8s.kubectl kubectl`.
-
-Download
-[telegraf.conf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf) and
-[telegraf-deployment.yml](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml) and set `containers.telegraf.image` in `telegraf-deployment.yml` to your chosen channel tag (e.g. `lts/telegraf:1.15-20.04_beta`), then:
-
-```sh
-kubectl create configmap telegraf-config --from-file=main-config=telegraf.conf
-kubectl apply -f telegraf-deployment.yml
-```
-
-You will now be able to connect to the Telegraf server on `localhost:30073`.
-
-## Bugs and feature requests
-
-If you find a bug in our image or want to request a specific feature, please file a bug here:
-
-[https://bugs.launchpad.net/ubuntu-docker-images/+filebug](https://bugs.launchpad.net/ubuntu-docker-images/+filebug)
-
-Please title the bug "`telegraf: <issue summary>`". Make sure to include the digest of the image you are using, from:
-
-```sh
-docker images --no-trunc --quiet lts/telegraf:<tag>
-```
-