v0.27.1

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.27.0 .
+docker build -t rustproxy:0.27.1 .
 ```
 
 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.27.0
+  rustproxy:0.27.1
 
 docker exec rustproxy rust-proxy admin setup-token
 ```
@@ -32,11 +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, 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.
+The runtime image includes Python, venv/pip, OpenSSL and distribution Certbot packages
+for Cloudflare, OVH and RFC2136 fallback. RustProxy prefers its own pinned Certbot
+environment under `/var/lib/rustproxy/acme-python`; because `/var/lib/rustproxy` is the
+persisted volume, that environment survives container replacement. If pip setup is not
+possible, the image can fall back to the distribution Certbot binaries already in `PATH`.
 
 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.