From 5609f5a6aff665b318667f6ff738fe2bc600b37b Mon Sep 17 00:00:00 2001 From: rcourtman Date: Mon, 15 Dec 2025 02:08:15 +0000 Subject: [PATCH] docs: fix Docker socket mount path for standalone sensor proxy The standalone installer creates the socket at /mnt/pulse-proxy on the host, not /run/pulse-sensor-proxy. Updated documentation to show the correct mount: /mnt/pulse-proxy:/run/pulse-sensor-proxy:ro Related to #822 --- docs/TEMPERATURE_MONITORING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/TEMPERATURE_MONITORING.md b/docs/TEMPERATURE_MONITORING.md index fed7f39..8214d24 100644 --- a/docs/TEMPERATURE_MONITORING.md +++ b/docs/TEMPERATURE_MONITORING.md @@ -30,8 +30,9 @@ If running Pulse in Docker, you must install the proxy on the host and share the Add the socket volume to your Pulse service: ```yaml volumes: - - /run/pulse-sensor-proxy:/run/pulse-sensor-proxy:ro + - /mnt/pulse-proxy:/run/pulse-sensor-proxy:ro ``` + > **Note**: The standalone installer creates the socket at `/mnt/pulse-proxy` on the host. Map it to `/run/pulse-sensor-proxy` inside the container. 3. **Restart Pulse**: `docker compose up -d`