Alpine Linux

Install the Runtime Sensor on Alpine Linux from the signed generic TGZ. Alpine does not use the Endura DEB or RPM repositories.

Prerequisites

Alpine Linux 3.23 on x86-64 (AMD64) hardware
Root or sudo access
Linux kernel 5.11 or later with BTF at /sys/kernel/btf/vmlinux
At least 1 GB of available memory
An Endura license key
Team Server URL and Runtime Sensor token for centralized management

Install the tools used by the installer:

sudo apk add curl gnupg

Install

The installer detects Alpine, downloads the TGZ and detached signature, and verifies it before extraction:

curl -sSf https://repo.endurasecurity.com/install/endura-sensor/testing.sh | sudo sh
endura version

Configure

Edit /opt/endura/sensor/environ:

sudo vi /opt/endura/sensor/environ

For Team Server mode, set:

ENDURA_LICENSE_KEY=your_license_key
ENDURA_TEAM_SERVER=https://team-server.example.com
ENDURA_SENSOR_TOKEN=your_sensor_token

Standalone use needs only the license. For Team Server, obtain an Administrator-issued token. Protect the file:

sudo chown root:root /opt/endura/sensor/environ
sudo chmod 600 /opt/endura/sensor/environ

See Configuration for optional variables.

Start and Verify

Direct startup on Alpine has no systemd mount helper. Mount the required kernel filesystems first:

sudo mkdir -p /sys/fs/bpf /sys/kernel/security
mountpoint -q /sys/fs/bpf || sudo mount -t bpf bpffs /sys/fs/bpf
mountpoint -q /sys/kernel/security || sudo mount -t securityfs securityfs /sys/kernel/security

Start the Sensor:

sudo sh -c 'set -a; . /opt/endura/sensor/environ; exec endura sensor start -d'
endura sensor wait
endura sensor status

The privileged shell loads the root-only environment file. Expect ok, then connectivity status. On startup failure, check the license and Sensor logs.

In Team Server, check Runtime Sensors. Deployments and workloads appear after a manually started workload is reported.

Operate the Runtime Sensor

# Status
endura sensor status

# Logs
sudo endura sensor logs -f

# Hook coverage
sudo endura sensor hooks

# Stop
sudo endura sensor stop

Update

Drain protected work before updating; restarts end enforcement and active jobs. Restart jobs after readiness and hook checks.

The TGZ installer preserves /opt/endura/sensor/environ, sets its mode to 0600, and does not restart the Runtime Sensor. Stop the Runtime Sensor, reinstall, and start it explicitly:

sudo endura sensor stop
curl -sSf https://repo.endurasecurity.com/install/endura-sensor/testing.sh | sudo sh
sudo sh -c 'set -a; . /opt/endura/sensor/environ; exec endura sensor start -d'
endura sensor wait
endura version

Review Team Server Compatibility before a major update.

Uninstall

Stop the Runtime Sensor first:

sudo endura sensor stop

The following commands remove Runtime Sensor configuration and logs

Back up any configuration or log data you need, then remove only the installed Runtime Sensor paths:

sudo rm -f /usr/bin/endura
sudo rm -f /etc/systemd/system/endura-sensor.service
sudo rm -f /etc/systemd/system/endura-kernel-filesystems.service
sudo rm -r /opt/endura/sensor
sudo rm -r /var/log/endura

Troubleshooting

Runtime Sensor Does Not Start

endura sensor status
sudo endura sensor logs -n 100
test -r /sys/kernel/btf/vmlinux && echo "BTF available"
uname -r

Check the license, environment-file permissions, BTF availability, and startup error.

Team Server Is Offline

curl -v https://team-server.example.com/_readiness
nslookup team-server.example.com

Confirm outbound TCP 443 and certificate trust. An incompatible state requires matching major versions; see Team Server Compatibility.

Installation Fails

gpg --version
df -h /opt
ldd /usr/bin/endura 2>/dev/null || true

Confirm that gnupg is installed and the target filesystem has space.

Configuration