v2.23 Preview Preview release - not for production v2024.1 STS Stable release with standard-term support v2.20 LTS Stable release with long-term support v2.18 STS Stable release with standard-term support v2.14 LTS Stable release with long-term support Unsupported versions

Software requirements for nodes

Operating system and additional software required for YugabyteDB

The Linux OS and other software components on each database cluster node must meet the following minimum software requirements.

Depending on the provider type and permissions you grant, you may have to install all of these requirements manually, or YugabyteDB Anywhere will install it all automatically.

Using disk encryption software with YugabyteDB

If you are using third party disk encryption software, such as Vormetric or CipherTrust, the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start before the encryption service, restarting an already encrypted node can result in data corruption.

To avoid problems, pause the universe before enabling or disabling the disk encryption service on universe nodes.

Linux OS

YugabyteDB Anywhere supports deploying YugabyteDB on a variety of operating systems.

AlmaLinux OS 8 disk images are used by default, but you can specify a custom disk image and OS.

Additional software

YugabyteDB Anywhere requires the following additional software to be pre-installed on nodes:

  • Python 3.6-3.8

  • Install the python selinux package corresponding to your version of python. For example, using pip, you can install as follows:

    python3 -m pip install selinux

    Alternately, if you are using the default version of python3, you might be able to install the python3-libselinux package.

  • OpenSSH Server. Allowing SSH is recommended but optional. Using SSH can be skipped in some on-premises deployment approaches; all other workflows require it. Tectia SSH is also supported.

  • tar

  • unzip

  • policycoreutils-python-utils

Additional software for airgapped deployment

Additionally, if not connected to the public Internet (that is, airgapped); and not connected to a local Yum repository that contains the additional software, database cluster nodes must also have the following additional software pre-installed:

  • libcgroup and libcgroup-tools (for planned future use of the cgconfig service, for cgroups; can be omitted for YBA versions earlier than v2024.1)
  • rsync, openssl (all linux)
  • semanage-utils (for Debian-based systems)
  • glibc-locale-source, glibc-langpack-en
  • libatomic (for Redhat-based aarch64)
  • libatomic1, libncurses6 (for Debian-based aarch64)
  • chrony (for time synchronization). When using a Public Cloud Provider, chrony is the only choice. When using an On-Premises provider, chrony is recommended, but ntpd is also an alternative option.