Improve temperature monitoring setup messaging for containerized deployments
When Pulse is running in a container and the SSH key is not available, provide clearer guidance about the pulse-sensor-proxy requirement and include documentation link for Docker deployments. This helps users understand that containerized Pulse needs the host-side sensor proxy to access temperature data from Proxmox hosts.
This commit is contained in:
parent
c3f31759c2
commit
d28cfed3c7
1 changed files with 9 additions and 1 deletions
|
|
@ -4409,7 +4409,15 @@ Host ${NODE}
|
|||
else
|
||||
echo ""
|
||||
echo "⚠️ SSH key not available from Pulse server"
|
||||
echo " Temperature monitoring cannot be configured automatically"
|
||||
if [ "$PULSE_IS_CONTAINERIZED" = true ]; then
|
||||
echo " Pulse is running in a container, so host-side temperature proxy is required."
|
||||
echo " Install pulse-sensor-proxy on the Proxmox host and bind-mount /run/pulse-sensor-proxy into the container."
|
||||
echo " After the proxy is online, rerun this setup script to push the SSH key."
|
||||
echo " Docs: https://github.com/rcourtman/Pulse/blob/main/docs/TEMPERATURE_MONITORING.md#quick-start-for-docker-deployments"
|
||||
else
|
||||
echo " Temperature monitoring cannot be configured automatically."
|
||||
echo " Ensure the Pulse service user has generated SSH keys and rerun this step."
|
||||
fi
|
||||
fi
|
||||
else
|
||||
echo "Temperature monitoring skipped."
|
||||
|
|
|
|||
Loading…
Reference in a new issue