Update docker.io/rcourtman/pulse Docker tag to v5.1.34
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.32 → 5.1.34 |
Release Notes
rcourtman/Pulse (docker.io/rcourtman/pulse)
v5.1.34: Pulse v5.1.34
✅ 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-02 12:10:50 UTC
Workflow: Pulse Release Pipeline #261
Validation Summary
- All required assets present ✓
- Checksums verified ✓
- Version strings correct ✓
- Binary architectures validated ✓
v5.1.34
Fixes
- Resolved a case where the same Ceph cluster was tracked under two internal identities when reported by both the Proxmox API and a Pulse host-agent. This could make pool alerts flap or duplicate and per-pool thresholds appear to revert. The cluster now resolves to a single identity. (#1341)
- Fixed repeated notifications for a single ongoing alert when the notification cooldown is disabled. A disabled cooldown now suppresses duplicate sends for the same active alert instead of re-notifying every cycle. (#1444)
Installation
If you run Pulse via Docker or Compose, update to rcourtman/pulse:5.1.34.
See the Installation Guide for other deployment methods.
v5.1.33: Pulse v5.1.33
✅ Release Asset Validation (Post-Publish): PASSED
Assets were revalidated after publication due to a release edit.
Status: Live release assets re-validated ✅
Validated: 2026-05-29 11:46:52 UTC
Workflow: Pulse Release Pipeline #259
Validation Summary
- All required assets present ✓
- Checksums verified ✓
- Version strings correct ✓
- Binary architectures validated ✓
v5.1.33
Fixes
- Added opt-in RBAC enforcement for Pulse Pro on v5.1.x. Roles can now be enforced from Settings > Access Control when an active Pro license includes RBAC.
- Fixed Proxmox guest memory selection for QEMU guest-agent payloads that report saturated Linux memory, using MemAvailable fallback where appropriate.
- Recorded the direct guest-agent memory value in diagnostic snapshots to make future memory-source debugging clearer.
Safety
- RBAC enforcement stays disabled by default so existing installations keep their current access behavior until an administrator enables it.
- RBAC enforcement can be disabled with
PULSE_RBAC_ENFORCEMENT=falseand a restart if recovery is needed.
Installation
If you run Pulse via Docker or Compose, update to rcourtman/pulse:5.1.33.
See the Installation Guide for other deployment methods.
