Safenix does not support installing the agent on a system that does not use systemd. The installation script can manage only a systemd service.
Why installation stops
The installer performs two checks before it changes anything on the machine:
- If the command required to manage systemd is not present, the installer stops and reports that systemd was not found.
- If systemd is installed but is not managing the machine, the installer stops and reports that starting a service would not work. This can happen, for example, inside a container.
In both cases, the installer stops without modifying the machine. These checks prevent it from leaving an agent program on disk that no service manager would start.
Supported option
Install the Safenix agent on a machine that uses systemd as its service manager. The most widely used Linux server distributions include systemd by default.
Having systemd installed is not enough if another process manages the machine. For example, a container may include systemd without using it as the system's service manager. That environment is not supported for agent installation.
Other service managers
Safenix does not provide an installation procedure for OpenRC, runit, or other startup systems. A server configured manually outside systemd would also not receive automatic updates, because those updates require systemd.
Therefore, there is no supported workaround for installing the Safenix agent on a non-systemd system. Use a systemd-based server for the installation.