Docker rcourtman/pulse:4.1.0 not saving Proxmox VE nodes

[oleksdovz]

Docker rcourtman/pulse:4.1.0 not saving Proxmox VE nodes
When I run pulse using docker and restart container

• list of Proxmox VE nodes is empty
• webhook present

• docker command

docker run -d \
  --name pulse \
  -p 7655:7655 \
  -v data:/data \
  -v config:/config \
  rcourtman/pulse:latest

• k8s statefulset yaml

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: pulse
  namespace: default
spec:
  selector:
    matchLabels:
      app: pulse
  serviceName: "pulse"
  replicas: 1
  template:
    metadata:
      labels:
        app: pulse
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: pulse
        image: rcourtman/pulse:v4.1.1
        ports:
        - containerPort: 7655
          name: pulse
        volumeMounts:
        - name: data 
          mountPath: /data
        - name: config 
          mountPath: /config
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      storageClassName: local-path
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi
  - metadata:
      name: config
    spec:
      storageClassName: local-path
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi          
---

[rcourtman]

thanks for reporting. the volume mapping looks correct - pulse stores everything in /data when running in docker, so you only need to mount that volume (the /config mount isn't used).

if nodes aren't persisting, check that your volume is actually persistent. for docker, use a named volume like:
docker run -d --name pulse -p 7655:7655 -v pulse-data:/data rcourtman/pulse:latest

for k8s, your volumeClaimTemplates look fine but make sure the PVCs are actually getting created and bound.

also, v4.1.1 has a much easier way to add nodes - just run the auto-registration script on your proxmox hosts and they'll add themselves to pulse automatically with all the right permissions. check the settings page for the setup script.

[oleksdovz]

Thank you for fast response,

• regarding pvc/pv, data is present in volume

# ls pvc-a70cecc6-425c-4b8f-bb5c-d8077cca9ed3_default_data-pulse-0
alerts  alerts.json  email.enc  nodes.enc  webhooks.json

root@n100:/data/k3s-storage# ls pvc-632e2b5a-ed55-4da5-b582-bf5fda837aab_default_config-pulse-0
--> no files

• logs from container
  Click to show code

kl -f pulse-0
Starting with UID: 1000, GID: 1000
9:32AM INF Generated new encryption key
9:32AM DBG Config persistence initialized configDir=/data encryptionEnabled=true nodesFile=/data/nodes.enc systemFile=/data/system.json
9:32AM INF Loaded system configuration interval=5000 updateChannel=
9:32AM INF Starting Pulse monitoring server
9:32AM INF Loaded alert history count=35
9:32AM INF Restored active alerts from disk restored=31 total=31
9:32AM DBG Config persistence initialized configDir=/data encryptionEnabled=true nodesFile=/data/nodes.enc systemFile=/data/system.json
9:32AM INF Alert configuration loaded file=/data/alerts.json
9:32AM INF Alert configuration updated
9:32AM INF Updated notification cooldown minutes=5
9:32AM INF Updated notification grouping window seconds=30
9:32AM INF Updated notification grouping options byGuest=false byNode=false
9:32AM WRN Failed to load email configuration error="cipher: message authentication failed"
9:32AM INF Webhooks loaded count=1 file=/data/webhooks.json
9:32AM INF Initializing PVE clients count=0
9:32AM INF Initializing PBS clients count=0
9:32AM DBG Config persistence initialized configDir=/data encryptionEnabled=true nodesFile=/data/nodes.enc systemFile=/data/system.json
9:32AM INF Serving frontend from staticDir=/app/frontend-modern/dist
9:32AM INF Starting monitoring loop pollingInterval=5000
9:32AM INF Starting background discovery service interval=300000 subnet=auto
9:32AM INF Discovery service initialized and started
9:32AM DBG Starting polling cycle
9:32AM DBG Polling cycle completed duration=0.014474
9:32AM INF Server listening host=0.0.0.0 port=7655
9:32AM INF Starting background discovery scan subnet=auto
9:32AM INF Starting network discovery subnet=auto
9:32AM INF Auto-detected local subnet detected=10.42.3.0/24
9:32AM INF IPs to scan count=254
9:32AM DBG Request handled duration=0.704887 method=GET path=/
9:32AM INF WebSocket upgrade request host=pulse1.lan origin=http://pulse1.lan userAgent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Safari/605.1.15"
9:32AM INF WebSocket client created client=client-1754818362574677301
9:32AM DBG Request handled duration=0.73916 method=GET path=/ws
9:32AM INF WebSocket client connected client=client-1754818362574677301
9:32AM INF WritePump started client=client-1754818362574677301
9:32AM INF ReadPump started client=client-1754818362574677301
9:32AM DBG Request handled duration=18.744694 method=GET path=/api/version
9:32AM INF Sending welcome message client=client-1754818362574677301
9:32AM INF Welcome message sent client=client-1754818362574677301
9:32AM INF Sending initial state to client client=client-1754818362574677301 dataKB=10 dataLen=10692
9:32AM INF Initial state sent successfully client=client-1754818362574677301
9:32AM DBG Request handled duration=0.321557 method=GET path=/
9:32AM INF WebSocket closed error="websocket: close 1001 (going away)" client=client-1754818362574677301
9:32AM INF ReadPump exiting client=client-1754818362574677301
9:32AM INF WebSocket client disconnected client=client-1754818362574677301
9:32AM DBG Send channel closed client=client-1754818362574677301
9:32AM INF WritePump exiting client=client-1754818362574677301
9:32AM INF WebSocket upgrade request host=pulse1.lan origin=http://pulse1.lan userAgent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Safari/605.1.15"
9:32AM INF WebSocket client created client=client-1754818363868818264
9:32AM DBG Request handled duration=1.229441 method=GET path=/ws
9:32AM INF ReadPump started client=client-1754818363868818264
9:32AM INF WebSocket client connected client=client-1754818363868818264
9:32AM INF WritePump started client=client-1754818363868818264
9:32AM DBG Request handled duration=9.366171 method=GET path=/api/version
9:32AM INF Sending welcome message client=client-1754818363868818264
9:32AM INF Welcome message sent client=client-1754818363868818264
9:32AM INF Sending initial state to client client=client-1754818363868818264 dataKB=10 dataLen=10692
9:32AM INF Initial state sent successfully client=client-1754818363868818264
9:32AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:32AM DBG Starting polling cycle
9:32AM DBG Polling cycle completed duration=0.105905
9:32AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:32AM DBG Starting polling cycle
9:32AM DBG Polling cycle completed duration=0.075787
9:32AM INF Discovery completed errors=0 found=0
9:32AM INF Background discovery scan completed errors=0 servers=0
9:32AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:32AM DBG Starting polling cycle
9:32AM DBG Polling cycle completed duration=0.630442
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.049641
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.204709
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.0778
9:33AM DBG Received WebSocket message client=client-1754818363868818264 type=pong
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.123155
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.085774
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.050767
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle
9:33AM DBG Polling cycle completed duration=0.087165
9:33AM INF Broadcasting state update (ticker) containers=0 nodes=0 pbs=0 pbsBackups=0 vms=0
9:33AM DBG Starting polling cycle

• can you please share link for auto-registration script or doc?
• docker image from latest release is not available for pull rcourtman/pulse:v4.1.1 https://github.com/rcourtman/Pulse/releases/tag/v4.1.1

[oleksdovz]

@rcourtman , I found what is missed, mount volume as /etc/pulse, after pod restart PVE nodes are showed on UI.

Like I miss this part in docs

File Locations

Configuration: /etc/pulse/ (or ./data if not writable)
system.json - UI-managed settings
.encryption.key - Auto-generated encryption key (do not share!) --> keys  re-creating  all time
nodes.enc - Encrypted node credentials
email.enc - Encrypted email settings
.env - Optional deployment overrides (if created)

there working yaml file for k8s

# https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: pulse
  namespace: default
spec:
  selector:
    matchLabels:
      app: pulse
  serviceName: "pulse"
  replicas: 1
  template:
    metadata:
      labels:
        app: pulse
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: pulse
        image: rcourtman/pulse:latest
        ports:
        - containerPort: 7655
          name: pulse
        volumeMounts:
        - name: data 
          mountPath: /data
        - name: etc-config 
          mountPath: /etc/pulse
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      storageClassName: local-path
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi
  - metadata:
      name: etc-config
    spec:
      storageClassName: local-path
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi                    
---

[rcourtman]

docker persistence works with volume mount: -v pulse_data:/data

[rcourtman]

Closing as fixed - Docker persistence issues resolved in v4.1.8.