How to update agents? #725
-
|
Apologies if I'm missing something obvious - how are agents (PVE and Docker) updated? I've just updated Pulse itself for the first time after the original installation to 4.31.0, and that went fine. Actually, come to think of it... have the agents been updated? Is there always a newer version bundled with the Pulse update? Or are they on a different version track? I'm quite unclear about this... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Docker agent auto-updates daily (and on restart) by pulling the latest binary from your Pulse server unless --no-auto-update/PULSE_NO_AUTO_UPDATE is set. For the containerized agent image (it sets PULSE_NO_AUTO_UPDATE=true), redeploy the container to get the new binary or flip that env var back to allow self-updates. Host/PVE agent doesn’t self-update. Rerun install-host-agent.sh from your Pulse server with the same URL/token; it downloads the current binary and restarts the service. No token rotation is needed unless you want to rotate credentials. If we ship a breaking or urgent agent change, we’ll call it out in the release notes; you’d just rerun the host installer or redeploy the Docker agent container where auto-update is disabled. |
Beta Was this translation helpful? Give feedback.
Docker agent auto-updates daily (and on restart) by pulling the latest binary from your Pulse server unless --no-auto-update/PULSE_NO_AUTO_UPDATE is set. For the containerized agent image (it sets PULSE_NO_AUTO_UPDATE=true), redeploy the container to get the new binary or flip that env var back to allow self-updates.
Host/PVE agent doesn’t self-update. Rerun install-host-agent.sh from your Pulse server with the same URL/token; it downloads the current binary and restarts the service. No token rotation is needed unless you want to rotate credentials.
If we ship a breaking or urgent agent change, we’ll call it out in the release notes; you’d just rerun the host installer or redeploy the Doc…