Unmeshed Logo

CLI & Remote Agents

Linux Agent Installation Guide

This guide covers the current native Linux agent workflow driven by the Unmeshed CLI.

The normal installation path is:

bash

Do not use the older Java-oriented agent install model for Linux. The current CLI manages native Linux agent binaries directly.

Prerequisites

Install the CLI on the Linux host first:

Run the installer

Start the install:

bash

The current installer prompts for:

  • the install directory
  • the service name
  • whether to install the latest version or select a recent version

Default values on Linux:

  • install directory: /unmeshed/agent
  • service name: unmeshedagent

What the installer creates

After the download completes, the Linux installer creates or records:

  • the native agent binary, for example unmeshed-agent-linux-amd64
  • the native monitor binary, for example unmeshed-monitor-linux-amd64
  • unmeshed.properties
  • processes.yaml
  • a generated launcher name derived from the service name, such as unmeshedagent-abc
  • an agent entry in ~/.unmeshed/config.yaml
  • a systemd unit at /etc/systemd/system/<service-name>.service

The systemd unit is created with:

  • WorkingDirectory=<install-dir>
  • ExecStart=/bin/bash -c '<install-dir>/<monitor-binary>'
  • Restart=always
  • User=<current-linux-user>
  • StandardOutput=append:<install-dir>/<service-name>.log
  • StandardError=append:<install-dir>/<service-name>.log

The CLI also sets UNMESHED_HOST_NAME in the service environment when it can determine the host name.

Configure the agent

Before starting the service, edit:

text

The current installer seeds these keys:

properties

UNMESHED_CUSTOM_TLS_CERTS_DIR points at the generated customcerts directory under the install path. If the agent must trust a self-signed or otherwise untrusted certificate chain, use Load certificates for self-signed or untrusted HTTPS endpoints.

Worker lists use this format:

text

Examples:

properties

The installer also creates processes.yaml, which points the monitor process at the generated agent launcher name for this service.

Enable and start the service

After updating unmeshed.properties, enable and start the systemd unit:

bash

Current day-2 service commands:

bash

If you need to re-display the current commands and status for an installed agent, use:

bash

Verification

Verify that the worker names you configured in unmeshed.properties appear as connected workers in the platform.

For list-agents, agent-info, update-agent, uninstall-agent, and offline agent update guidance, see Remote Agent Lifecycle.

Offline installation

If the target Linux machine cannot reach the CLI or agent download hosts directly, use Download the CLI for another machine to stage the CLI binary and Install from local binaries to install the agent from copied binaries.

After install-agent --use-local-binaries completes, continue with the normal configuration and systemd steps in this guide.

Related Documentation