Installing the agent
For the first connection, follow the quickstart. This page covers installation options and changing agent permissions.
Command
Section titled “Command”FLOTERA_INIT_TOKEN=erm_init_... /bin/bash -c "$(curl -fsSL https://get.flotera.com)"Copy the complete command from Servers → Add server (or Add server on the Dashboard while the fleet is empty). The one-time token registers the server in your account. Each new server requires a new token.
Use the panel command without changing how it passes the token. Do not share it: the token authorizes server registration.
Installation steps
Section titled “Installation steps”- Permission choice:
read-onlyorfull. If you are not root, the installer then asks forsudoonce: steps 2–6 run as root. - Server check: system, driver, and network.
- Agent download: downloading the current release and verifying its signature and checksum.
- Helper package installation:
smartmontoolsandnvme-cli. If they cannot be installed, installation continues without SMART disk data. - Service installation: a system user, the service, and the agent files.
- Agent start: the installer starts the service and checks that it is running. The panel detects the server once the agent connects.
The result of each step is printed to the terminal. If a step fails, save the message and the step number for diagnostics.
Agent permissions
Section titled “Agent permissions”Collects GPU, temperature, power draw, memory, disk, and network data. Hardware control is unavailable.
Collects data and controls hardware: power limit, fan policy, server reboot, and power off.
When run without an interactive terminal, for example through Ansible or cloud-init,
read-only is used by default.
Changing permissions
Section titled “Changing permissions”Rerun the installer with the required --privilege value:
FLOTERA_INIT_TOKEN=erm_init_... /bin/bash -c "$(curl -fsSL https://get.flotera.com)" -- --privilege fullIn command-line options, read-only mode is written as readonly.
Options
Section titled “Options”| Option | Default | Purpose |
|---|---|---|
FLOTERA_INIT_TOKEN=TOKEN |
required for the first install | one-time registration token, set in the environment before the command |
--token-stdin |
— | read the token from the first line of standard input instead of the environment (for automation) |
--privilege LEVEL |
asks the user, otherwise readonly |
full or readonly |
--target WHERE |
host |
host or container |
--token TOKEN is not accepted: the installer refuses a token passed as an
argument.
Installing in a rented instance
Section titled “Installing in a rented instance”The --target container option is intended for a GPU container at a
third-party provider, such as Vast.ai or RunPod. Only read-only is allowed: combining it with --privilege full fails with an error,
because host hardware control is unavailable in this mode.
Rerunning the installer
Section titled “Rerunning the installer”Reinstallation updates files and configuration while preserving credentials and the command journal. Use it to change permissions, complete an interrupted installation.
For a regular version update, the panel is sufficient.
NVIDIA driver
Section titled “NVIDIA driver”The agent installer does not install or update the driver, and the panel cannot do it either. Install and update the driver yourself, between rentals: an update may require a reboot.