Supported operating systems

Puppet Enterprise supports various operating systems depending on the role a machine assumes in your infrastructure.

Supported operating systems and devices

You can install PE and the agent on these supported platforms.

For details about platform support lifecycles and planned end-of-life support, see Platform support lifecycle on the Puppet website.

Important: If you implement Linux hardening techniques, consider customizing your settings, including but not limited to the following:

SELinux: Grant exceptions for Puppet and the PXP agent to allow these services to run effectively.
File Access Policy Daemon (fapolicyd): Grant exceptions for PE services to prevent potential restrictions.
umask: Ensure your operating system's default umask is set to 022 or less restrictive. A more restrictive setting can lead to unintended failures, as Puppet users might be denied access to necessary files.

Primary server platforms

The PE primary server can be installed on the following operating systems. All primary server platforms require an x86_64 architecture (or amd64 for Ubuntu).

CAUTION: Major primary server OS upgrades (such as Ubuntu 18.04 to 20.04) require Back up and restore PE.


Operating system	Versions
AlmaLinux	8
Amazon Linux	2
CentOS	7
Oracle Linux	7
Red Hat Enterprise Linux	7, 8, 9
Red Hat Enterprise Linux (FIPS 140-2 compliant)	7, 8
Rocky Linux	8
Scientific Linux	7
SUSE Linux Enterprise Server	12, 15
Ubuntu (General Availability kernels)	18.04, 20.04, 22.04

Agent platforms

The agent can be installed on these operating systems and architectures.

CAUTION: Major agent OS upgrades (such as Ubuntu 18.04 to 20.04) require reinstalling the puppet-agent package (as explained in Installing agents) and reinstalling any Ruby plugins/gems that were added at /opt/puppetlabs/puppet/bin/gem.


Operating system	Versions	Architecture
AIX	7.2, 7.3 Note: We support only technology levels that are still under support from IBM.	POWER
AlmaLinux	8	x86_64, aarch64, ppc64le
Amazon Linux	2, 2023	2: x86_64 2023: amd64, aarch64
CentOS	7	x86_64
Debian	Buster (10), Bullseye (11), Bookworm (12)	10: amd64 11: amd64, aarch64 12: amd64, aarch64
Fedora	36	x86_64
macOS	11, 12, 13, 14	11: x86_64 12: x86_64, M1 13: x86_64, ARM 14: x86_64, ARM
Microsoft Windows	10, 11	10: x86, x64 11: x64 For FIPS 140-2 compliant Microsoft Windows, use version 10 with x64 architecture.
Microsoft Windows Server	2012, 2012 R2, 2012 R2 Core, 2016, 2016 Core, 2019, 2019 Core, 2022	x64 For FIPS 140-2 compliant Microsoft Windows Server, use 2012 R2 or 2012 R2 core.
Oracle Linux	7, 8, 9	7: x86_64 8: x86_64, aarch64, ppc64le 9: x86_64
Red Hat Enterprise Linux	7, 8, 9	7: x86_64 8: x86_64, aarch64, ppc64le 9: x86_64, ARM64 For FIPS 140-2 compliant RHEL, use version 7, 8, or 9 with x86_64 architecture.
Rocky Linux	8	x86_64, aarch64, ppc64le
Scientific Linux	7	x86_64
Solaris	11	SPARC, x86_64
SUSE Linux Enterprise Server	12, 15	x86_64
Ubuntu (General Availability kernels)	18.04, 20.04, 22.04	18.04: amd64, aarch64 20.04: amd64, aarch64 22.04: amd64, ARM64

Platform dependencies

When you install PE or an agent, certain package dependencies are required to ensure the node is operational.

In most cases, dependencies are automatically set up during installation. You might need to manually install dependencies in these cases:

If you're installing on AIX or Solaris.
If the node doesn't have internet access.

Note: Some operating systems require an active subscription with the vendor's package management system (for example, the Red Hat Network) to install dependencies.

CentOS dependencies


	All nodes	Primary server
cronie	x	x
dmidecode	x	x
libxml2	x	x
logrotate	x	x
net-tools	x	x
pciutils	x	x
tar	x	x
which	x	x
zlib	x	x
curl		x
libjpeg		x
libtool-ltdl (versions 7 and later)		x
libxslt		x
mailcap		x

RHEL dependencies


	All nodes	Primary server
cronie	x	x
dmidecode	x	x
libxml2	x	x
logrotate	x	x
net-tools	x	x
pciutils	x	x
tar	x	x
which	x	x
zlib	x	x
curl		x
libjpeg		x
libtool-ltdl (versions 7 and later)		x
libxslt		x
mailcap		x
initscripts		x

SUSE Linux Enterprise Server dependencies

Tip: If you encounter problems installing dependencies, inspect the error messages for packages that require other SUSE Linux Enterprise Server packaging modules to be enabled, and use

zypper package-search
                        <PACKAGE NAME>

to locate them for manual installation.


	All nodes	Primary server
cron	x	x
libxml2	x	x
libxslt	x	x
logrotate	x	x
net-tools	x	x
pciutils	x	x
pmtools	x	x
tar	x	x
zlib	x	x
curl		x
db43		x
libjpeg		x
unixODBC		x

Ubuntu dependencies


	All nodes	Primary server
cron	x	x
dmidecode	x	x
gnupg	x	x
hostname	x	x
libldap-2.4-2	x	x
libreadline5	x	x
libxml2	x	x
logrotate	x	x
pciutils	x	x
tar	x	x
zlib	x	x
ca-certificates-java		x
curl		x
file		x
libcap2		x
libgtk2.0-0		x
libjpeg62		x
libmagic1		x
libossp-uuid16		x
libpcre3		x
libxslt1.1		x
mime-support		x
perl		x

AIX dependencies

AIX is a supported platform for the agent only. Before installing the agent on AIX systems, install these packages.

bash
curl
openssl
readline
tar
zlib

For information about installing these packages, see AIX Toolbox for Open Source Software.

Restriction: For OpenSSL, you must use the version provided by IBM Marketing Registration Services (MRS). For more information, see the IBM support docs about Downloading and Installing or Upgrading OpenSSL and OpenSSH.

Solaris dependencies and limitations

Solaris support is agent only.

For Solaris 11 these packages are required:

system/readline
system/library/gcc-45-runtime
library/security/openssl
tar

These packages are available in the Solaris release repository, which is enabled by default in version 11. The installer automatically installs these packages; however, if the release repository is not enabled, the packages must be installed manually.

Upgrade your operating system with PE installed

If you have PE installed, take extra precautions before performing a major upgrade of your machine's operating system.

Performing major upgrades of your operating system with PE installed can cause errors and issues with PE. A major operating system upgrade is an upgrade to a new whole version, such as an upgrade from RHEL 6.0 to 7.0; it does not refer to a minor version upgrade, like RHEL 6.5 to 6.6. Major upgrades typically require a new version of PE.

Back up your databases and other PE files.
Perform a complete uninstall (using the -p and -d uninstaller options).
Upgrade your operating system.
Install PE.
Restore your backup.

Was this page helpful?

We’re sorry to hear that!
Please tell us why so we can help. Enter your feedback and email. This form is sent to the Puppet docs team. We ask for your email as we might contact you regarding your feedback. If you need help with the product itself, visit Puppet Support or ask in Puppet Community on Slack. Feedback:

Email Address:

To learn about how Puppet uses your personal information, visit our privacy policy.

If you leave us your email, we may contact you regarding your feedback. For more information on how Puppet uses your personal information, see our privacy policy.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project.