Skip to main content
This page documents Anaconda’s policies for platform and operating system support. In this policy, “platform” refers to the combination of operating system and CPU architecture that Anaconda builds packages for, corresponding to Anaconda’s subdirectory naming convention (for example, linux-64, win-64, osx-arm64).

Currently supported platforms

These platforms receive full support, including new package additions, package updates, security fixes, and installer releases.

Maintenance Support

Anaconda does not currently have any platforms in maintenance support status. This category applies when Anaconda determines that a platform will be discontinued but wishes to provide a transition period with security updates and critical bug fixes only before complete end of support. Platforms might enter maintenance status based on factors including vendor lifecycle changes, declining user adoption, or upstream ecosystem constraints.

Discontinued Platforms

These platforms no longer receive Anaconda support. There will be no new package additions, package updates, security fixes, or installer releases. Issues with packages on these platforms will not be investigated. The packages we have already built will remain available for use.

Platform Specific Considerations

Anaconda builds packages against specific operating system baselines that define minimum compatibility requirements. This section documents the technical assumptions Anaconda makes about each platform’s environment, including C standard library versions, operating system requirements, and other platform-specific dependencies. These baselines ensure packages function reliably while maintaining broad compatibility across supported systems.

Windows

Anaconda performs Quality Assurance testing on Windows operating systems to validate our package distribution. When you report issues on supported Windows versions, Anaconda will investigate and work to resolve them. However, if an upstream package maintainer introduces breaking changes that affect compatibility, resolution might require coordination with that maintainer or might fall outside Anaconda’s direct control, though we will make best efforts to work with upstream maintainers on these problems.

Windows Client

Anaconda supports Windows versions that are within Microsoft’s support lifecycle for Enterprise and Education editions. *Anaconda is providing extended support past the Microsoft end of support date for Windows 10 22H2 to support customer transitions. This decision predates this formal policy. After the end of support dates above, Anaconda will no longer verify that new package releases function correctly on these operating systems, and bug reports specific to these versions will not be addressed. Packages built for supported Windows versions might function on older versions, but Anaconda does not test against or provide support for end-of-life Windows releases. Previously built packages remain available in our repositories, and existing environments will continue to function. For users on Windows Home and Pro editions, Anaconda recommends upgrading to newer Windows versions as soon as Microsoft ends support for your current version to maintain security updates from Microsoft.

Windows Server

Anaconda supports Windows Server versions through Microsoft’s extended support lifecycle (not extended security updates). After the end of the support dates above, Anaconda will no longer verify that new package releases function correctly on these operating systems, and bug reports specific to these versions will not be addressed. Packages built for supported Windows versions might function on older versions, but Anaconda does not test against or provide support for end-of-life Windows releases. Previously built packages remain available in our repositories, and existing environments will continue to function.
Important: Windows Server support timelines are independent of Windows Client support timelines. Enterprise customers typically run Windows Server editions through Microsoft’s extended support period, during which Microsoft continues to provide security updates. While Anaconda aligns our Windows Server support with these extended timelines, this does not extend support for Windows 10 or Windows 11 client editions, which follow Microsoft’s shorter support lifecycle for consumer and professional operating systems. If you are running Windows 10 or Windows 11 client editions, refer to the Windows Client support table above for applicable end dates and plan to upgrade when Microsoft ends security updates for your version.

macOS

Anaconda performs Quality Assurance testing on macOS to validate our package distribution. When you report issues on supported macOS versions, Anaconda will investigate and work to resolve them. However, if an upstream package maintainer introduces breaking changes that affect compatibility, resolution might require coordination with that maintainer or might fall outside Anaconda’s direct control, though we will make best efforts to work with upstream maintainers on these problems. Anaconda supports the three most recent major releases of macOS: Apple does not publish explicit end-of-life dates for macOS versions, but they typically cease providing security fixes when a release falls out of the three latest versions. You can reference macOS release dates here.

Linux

C Standard Library baseline: glibc 2.28

Anaconda packages for Linux are built against glibc 2.28 as the baseline. This version is included in Red Hat Enterprise Linux 8, Ubuntu 20.04, and most Linux distributions released after 2019. Packages built against glibc 2.28 will run on systems with glibc 2.28 or later. They might not function on older systems with earlier glibc versions. Anaconda aligns glibc requirements with the oldest actively supported enterprise Linux distribution. We will provide at least 12 months notice before increasing glibc requirements. The next glibc baseline update is not expected before 2029, when Red Hat Enterprise Linux 8 reaches end of maintenance support on May 31, 2029 (Source).

Exception

Some packages might require glibc versions newer than 2.28 due to upstream build requirements. When this occurs:
  • Conda will check your system’s glibc version during installation.
  • If your system doesn’t meet the requirement, conda will prevent installation with a clear error message.
If you encounter a glibc requirement error, recommended options are:
  • Upgrade to a newer Linux distribution.
  • Use an older version of the package that’s compatible with glibc 2.28, if available.