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 critical prerequisites https //docs swimlane com/turbine installer/embedded cluster install/system requirements for an embedded cluster install/system requirements for an embedded cluster install htm 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 quay io http //quay io/ remote agent installation typically downloads a bash script from your swimlane turbine instance during installation, several containers will be downloaded from quay io quay io http //quay io/ they may also be downloaded during cron based upgrades connectors are not downloaded from quay io 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 install docker https //docs docker com/engine/install/ docker service and client required; no license needed agent auto restarts after os reboot by default podman install 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 install python 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 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 docker post install https //docs docker com/engine/install/linux postinstall/ podman rootless troubleshooting https //github com/containers/podman/blob/main/troubleshooting md#17 rootless containers exit once the user session exits podman and os integration by default, podman does not automatically boot hosted containers during a system restart for systemd based auto restart, see redhat documentation https //www redhat com/sysadmin/container systemd persist reboot you may also need to enable session linger for non root installations loginctl enable linger $(whoami)