Requirements and Pre-Installation

user permission requirements must be an account admin in swimlane multi factor authentication (mfa) must be disabled for installation, or use the " exempt force sso " option if mfa is enabled the user used for installation is not saved, and may be removed after installation instead, machine ids and secrets are created during installation for agent communication supported operating systems for the latest supported os list, see docid 9lxricxlm1t14ydlkt4zr hardware requirements resource minimum cpu 2 vcpus (x64) ram 2 gb disk os minimum + 20 gb additional hardware may be required dependent on workload and specific processing requirements network requirements outbound https (443) to your swimlane turbine instance and quay io whitelist all of http //quay io/ remote agent installation typically downloads a bash script from your swimlane turbine instance during installation, several containers will be downloaded from http //quay io/ they may also be downloaded during cron based upgrades connectors are not downloaded from http //quay io/ and are instead pulled from the primary swimlane turbine instance required software you must install docker (latest) or podman 4 2+ (only one required) docker https //docs docker com/engine/install/ docker service and client required; no license needed agent auto restarts after os reboot by default podman https //access redhat com/documentation/en us/red hat enterprise linux/8/html single/building running and managing containers/index#proc getting container tools assembly starting with containers additional packages such as podman plugins may be required depending on the installation method while you can install either docker (latest) or podman 4 2+ to run the remote agent, docker is recommended for most users as it is generally easier to get started with podman is better suited for advanced system administrators python 3 https //www python org/downloads/ os level requirements remote agents heavily use container technology to run isolated workloads different linux os distributions come with different default settings for container namespaces control groups v2 (cgroup v2) only cgroup v2 is supported remote agents require cgroup v2 for proper resource management and rootless container nesting most modern distributions (rhel 9, rocky linux 9, amazon linux 2023) use cgroup v2 by default if your system is configured for cgroup v1 or "hybrid" mode, the agent installation will fail maximum user namespaces before running the install script, verify and/or set the maximum user namespaces sudo sysctl user max user namespaces=65536 user namespaces allow containers to run as non root users selinux and non root installs for rhel/selinux or non root scenarios, follow the container engine post install docs https //docs docker com/engine/install/linux postinstall/ https //github com/containers/podman/blob/main/troubleshooting md#17 rootless containers exit once the user session exits podman and operating system integration podman remote agents can now be managed using quadlets , providing improved operating system integration and reliability quadlets are exclusive to podman and are not compatible with docker when installing remote agents with podman, use the q flag to enable quadlet support to migrate existing podman remote agents, disable and remove any existing systemd configurations, then add q flag to the update script crontab supported operating systems for quadlets rhel 9 9 2, 9 4, 9 5, 9 6 rocky linux 9 9 2, 9 4 supported podman version 4 4+ this enhancement ensures that podman remote agents restart seamlessly with the system and are fully supported through quadlet based management note that all remote agents in a host or system should either be in quadlet mode or non quadlet mode but not both