Merge pull request #738 from openziti/docker-instance-prune-troublesh…

…ooting-advice

prune docker instance troubleshooting advice

CHANGELOG.md

@@ -1,5 +1,9 @@
 # CHANGELOG
 
+## v0.4.40
+
+FIX: prune incorrect troubleshooting advice about listing Caddy's certificates
+
 ## v0.4.39
 
 FEATURE: New API endpoint allowing direct creation of accounts in the zrok database. Requires an admin token (specified in the controller configuration yaml) for authentication. See the OpenAPI spec for details of the API endpoint. The `zrok admin create account` CLI was also updated to call the API endpoint, rather than directly operating on the underlying database (https://github.com/openziti/zrok/issues/734). The [Docker](https://github.com/openziti/zrok/pull/736) and [Kubernetes](https://github.com/openziti/helm-charts/pull/249) zrok instance deployments were adapted to the new CLI parameter shape.

docker/compose/zrok-instance/README.md

@@ -214,14 +214,6 @@ The `ziti-quickstart` and `caddy` containers publish ports to all devices that u
     dns.providers.cloudflare
     ```
 
-1. Verify certificates.
-
-    You can check the certificates that Caddy has obtained.
-
-    ```bash
-    docker compose exec caddy caddy list-certificates
-    ```
-
 1. Use the Caddy admin API.
 
     You can use the Caddy admin API to check the status of the Caddy instance. The admin API is available on port `2019/tcp` inside the Docker Compose project. You can modify `compose.override.yml` to publish the port if you want to access the admin API from the Docker host or elsewhere.