mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
rcourtman
c2f6848006
lxc-attach into an unprivileged guest writes /proc/<pid>/uid_map, which needs CAP_SETUID in the parent user namespace. NoNewPrivileges drops CAP_SETUID from the effective set and also stops lxc-attach falling back to the setuid newuidmap/newgidmap helpers, so the socket probe dies with "write_id_mapping: 61 Operation not permitted". install.sh already relaxed NoNewPrivileges for this, but only when the agent was installed with --enable-commands. Command execution is also togglable from the server afterwards: applyRemoteConfig starts the command client without rewriting the unit. An agent installed without the flag and switched on later therefore ends up able to run commands and unable to attach to unprivileged guests, so Docker inside every unprivileged LXC disappears from the Proxmox page. The probe failure is logged at debug level and retried on every poll, so the surface looks empty rather than broken while the agent re-probes the whole guest list. Grant CAP_SETUID/CAP_SETGID to any PVE agent rather than gating on the install-time flag, so the later toggle lands on a unit that can attach. Ambient capabilities restore exactly the privilege lxc-attach needs and leave the rest of the sandbox intact; the existing install-time relaxation is unchanged. Verified on a live PVE node. With the hardened unit the probe succeeded only on the three privileged guests and failed on every unprivileged one. After the ambient grant CapEff regained CAP_SETUID and both unprivileged Docker guests were discovered, taking that node from one Docker LXC to three.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.