Installation

install a remote agent on a docker or podman host by copying the install script from turbine and running it on the target machine choose your path i want to… start here install with docker or standard podman install a remote agent /#install a remote agent install with podman quadlet (systemd lifecycle) use podman quadlet /#use podman quadlet pull connector images from my own registry pull connector images from an override registry /#pull connector images from an override registry review install fields and flags configuration options /#configuration options install a remote agent open admin panel > settings > tenant > nodes click view agents to see your agents and pools open the install an agent dialog fill in the required fields see configuration options /#configuration options click copy install script paste the script into a terminal on the target host and run it as a user that can start containers (and systemd, if you use quadlet) complete any prompts the script can ask for turbine credentials; credentials are not saved do not click outside the install dialog before you copy the script closing the dialog resets the generated command sample install command pattern curl k https //\<your turbine instance>/agent/install sh | bash s n 'my agent' s '0 /4 ' configuration options ui field or flag description agent name ( n ) required letters, numbers, hyphen, or underscore only do not use spaces ca cert path ( c ) folder of ca certificates for self signed or internal tls validation agent initial pools ( o ) comma delimited pools to join at install time you can add more than one agent container network subnet ( n ) container network subnet in cidr format default 10 55 55 0/24 http proxy / https proxy / no proxy proxy settings for outbound agent traffic wildcards are not supported in no proxy cron schedule ( s ) cron expression for automatic agent image updates ignore insecure certificates instructs the agent and its connectors to ignore insecure certificates when connecting to https sources allow insecure certificates for gateway communication allows an insecure certificate when connecting to the turbine agent gateway use podman quadlet ( q ) see use podman quadlet /#use podman quadlet podman only available in turbine 26 3 0 b / c override registries for swimlane and custom connector images script only see pull connector images from an override registry /#pull connector images from an override registry available in turbine 26 3 0 additional options may be available only on the command line run the install script with help for the full usage list use podman quadlet starting in turbine 26 3 0 , the install an agent dialog includes use podman quadlet when enabled, the generated install command adds the q flag so the agent runs as a systemd quadlet for os integrated lifecycle management requirement detail container runtime podman only the install script validates that podman is present when q is set podman version podman 4 4 or later recommended platforms rhel 9 or rocky linux 9 ui toggle use podman quadlet — hint text in the product matches this requirement script flag q — use podman quadlets for managing agent containers enable quadlet from the ui open the install an agent dialog complete required fields such as agent name turn on use podman quadlet click copy install script run the script on a podman 4 4+ host enable quadlet from the script add q when you install or reinstall with podman \# example fragment — include your full t, n, and other required flags bash s t '\<turbine url>' n 'my agent' q s '0 /4 ' for docker based hosts, leave use podman quadlet off quadlet is a podman and systemd integration quadlet unit files live under /etc/containers/quadlets/ for root and under {home}/ config/containers/systemd for non root after you change quadlet files manually, run systemctl daemon reload pull connector images from an override registry starting in turbine 26 3 0 , remote agents can pull connector images from an override registry or namespace instead of only through the agent gateway this supports environments that must run self hosted or pre scanned images use these install script flags (add them to the install command manually; they are not toggles on the install an agent dialog) flag description b override registry and namespace for swimlane connector images the agent pulls those images directly from the override location instead of through the agent gateway c override registry and namespace for custom connector images same direct pull behavior for non swimlane connector images example pattern bash s t '\<turbine url>' n 'my agent' \\ b 'registry example com/swimlane connectors/' \\ c 'registry example com/custom connectors/' the install script sets agent environment variables such as container image path swimlane and container image path custom from b and c registry authentication for image pulls is tracked separately ( spt 65951 https //swimlane atlassian net/browse/spt 65951 ) confirm credential setup for your registry with your platform team before you rely on private registries in production preflight checks during installation, the script runs several checks watch for warnings or errors warnings or errors may not block installation, but they can affect stability or performance checks performed primary swimlane turbine system connection login credentials image access from quay io https //quay io/ (or other image repositories you provide) cgroup v2 enablement container host version, function, and storage size ability of the container host to run an image quality of connection to the turbine environment (including latency) virtual container network settings conflicting containers or networks on the container host related guides remote agents https //docs swimlane com/remote agentsviewing remote agents https //docs swimlane com/viewing remote agentsuninstall remote agent https //docs swimlane com/uninstall remote agent