Debian / Ubuntu
Install the LinuxGuard agent on Debian, Ubuntu, and derivatives via the APT repository at packages.linuxguard.io.
This guide covers repository-based installation on Debian, Ubuntu, and derivatives (such as Linux Mint).
Note: Supported architectures — Debian/Ubuntu packages ship for
amd64,arm64, andarmv7. ARMv7 deployments run inDegradedNoEBPFArchmode with no eBPF-derived telemetry. See Multi-Architecture Support for the per-architecture capability matrix.
Prerequisites
Linux kernel 4.18+ (for eBPF support)
Root or sudo access
Outbound HTTPS access to
packages.linuxguard.io
Note: See Prerequisites for full system requirements.
Repository Setup
The recommended installation method uses the official LinuxGuard APT repository. This ensures you receive automatic updates and can easily manage the agent through your package manager.
Step 1: Install Prerequisites
Install required packages for repository configuration:
sudo apt install curl ca-certificates gnupgStep 2: Import GPG Key
Create the keyrings directory and import the LinuxGuard signing key:
Step 3: Add Repository
Add the LinuxGuard repository to your system:
Step 4: Install Agent
Update the package index and install the agent:
The agent service will be installed but not started until enrollment.
Direct Download
If repository setup is not possible, you can download and install the package directly:
ARM64 installation
The APT repository at packages.linuxguard.io/apt publishes both amd64 and arm64 packages under the same deb line. The repository setup snippet in Step 3 already pins the architecture via arch=$(dpkg --print-architecture), so an arm64 (aarch64) host pulls the arm64 package without further configuration.
To confirm your host is arm64 before installing:
The arm64 package ships the same agent binary + compiled eBPF probe object as the amd64 package — arm64 is a full-eBPF architecture per the capability matrix. No degradation, no missing telemetry.
If your host is ARMv7 (armv7l, armhf), the package is still available via the APT repository but the agent runs in Degraded mode — the eBPF probe is a zero-byte sentinel and no behavioral telemetry is produced. The dpkg --print-architecture value on an ARMv7 host is armhf, and the repository serves the corresponding package. Treat ARMv7 hosts as a documented gap in the evidence chain.
Note: For containerized arm64 deployments (Kubernetes DaemonSet on an arm64 node pool, Docker on an arm64 host), the OCI multi-arch manifest selects the arm64 image automatically when pulling
packages.linuxguard.io/linuxguard-agent:vX.Y.Z. See OCI multi-arch manifest for the manifest inspection and--platformpull syntax.
Verification
After installation, verify the agent is correctly installed:
Check Agent Binary
Confirm the agent binary is in your PATH:
Expected output:
Verify Agent User
Confirm the agent user and group were created:
Expected output:
Note: The UID/GID numbers may vary depending on your system.
Check Service Status
Verify the agent service is installed:
Expected output:
The service is inactive until you complete enrollment.
Troubleshooting
Repository Not Found
If apt update fails to find the LinuxGuard repository, verify the repository file exists:
The file should contain the repository configuration with the correct architecture.
GPG Key Errors
If you encounter GPG signature verification errors, verify the key was imported correctly:
If the file is missing, repeat Step 2 of the repository setup.
Package Conflicts
If installation fails due to conflicting packages, check for unofficial or third-party LinuxGuard packages:
Remove any unofficial packages before installing from the official repository.
Note: See the Troubleshooting Guide for additional help.
Next Step: Configuration →
Related: Installation Overview | Prerequisites | Troubleshooting
Last updated
Was this helpful?