v0.26.7

docs/CONTAINER.md

@@ -9,7 +9,7 @@ each Docker host, so the proxy container never needs Docker-socket access. See
 Build locally with a normal OCI builder:
 
 ```bash
-docker build -t rustproxy:0.22.3 .
+docker build -t rustproxy:0.26.7 .
 ```
 
 Persist `/var/lib/rustproxy`; it contains the SQLite database, certificates and the
@@ -22,7 +22,7 @@ docker volume create rustproxy-data
 docker run --rm -d --name rustproxy \
   -p 8080:8080 \
   -v rustproxy-data:/var/lib/rustproxy \
-  rustproxy:0.22.3
+  rustproxy:0.26.7
 
 docker exec rustproxy rust-proxy admin setup-token
 ```
@@ -32,10 +32,11 @@ RustProxy configuration and choose a certificate, then bind the administration
 listener to a non-loopback address. Publish the admin port only after HTTPS is
 active. Plain remote HTTP keeps the legacy explicit risk gate.
 
-The runtime image includes Python, Certbot and OpenSSL for the built-in HTTP-01
-certificate helper. Provider-specific Certbot DNS plugins are not installed in the
-baseline image; extend the image with the required plugin package before using a DNS
-provider.
+The runtime image includes Python, OpenSSL and a dedicated Certbot environment with
+all DNS plugins currently supported by RustProxy: Cloudflare, OVH and RFC2136.
+HTTP-01 needs no DNS plugin. The Certbot core and all three DNS plugins are pinned to
+the same release so they stay in one compatible Python environment; no image extension
+is required for the built-in certificate providers.
 
 For access-log files, prefer a writable path under `/var/lib/rustproxy` or mount a
 separate writable log volume. The built-in JSON file sink is disabled by default.