Update docker.io/rcourtman/pulse Docker tag to v5.1.35

Share
Update docker.io/rcourtman/pulse Docker tag to v5.1.35
Photo by Joshua Chehov / Unsplash

No problems upgrading the Docker container with a Docker compose yaml file by means of Watchtower DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot.
Including updating all docker and host agents manually.

This MR contains the following updates:

Package Update Change
docker.io/rcourtman/pulse patch 5.1.345.1.35

Release Notes

rcourtman/Pulse (docker.io/rcourtman/pulse)

v5.1.35: Pulse v5.1.35

Compare Source

✅ Release Asset Validation (Post-Publish): PASSED

Assets were revalidated after publication due to a release edit.

Status: Live release assets re-validated ✅
Validated: 2026-06-11 09:50:29 UTC
Workflow: Validate Release Assets #​87

Validation Summary
  • All required assets present ✓
  • Checksums verified ✓
  • Version strings correct ✓
  • Binary architectures validated ✓
Pulse v5.1.35

Final v5 maintenance release ahead of Pulse v6.

Security
  • Agent updater no longer forwards the agent API token (X-API-Token) when a
    configured Pulse server issues a cross-host redirect. The updater now refuses
    to follow redirects rather than re-sending credentials to the redirect
    target (GHSA-v644-29mm-jwx3). Reported by tonghuaroot.
Fixes
  • Ceph pool overrides now resolve consistently across reporting sources, fixing
    pool alert configuration disappearing from the Alerts tab and intermittent
    Proxmox cluster metric gaps.
  • Proxmox hosts that become unreachable now stay visible on the dashboard with
    their nodes marked offline, instead of freezing at their last online snapshot
    or never appearing when the host was already down at Pulse startup.
Installation

If you run Pulse via Docker or Compose, update to rcourtman/pulse:5.1.35.

See the Installation Guide for other deployment methods.

Read more

Me on Mastodon - This link is here for verification purposes.