Announcing the Linux package archive site

HashiCorp will cease publishing packages of our products for end-of-life (EoL) distributions to our production packaging sites and migrate EoL versions to our new archive site.

On January 10th, 2024, HashiCorp will no longer support versions of Linux operating systems that have reached end-of-life (EoL) status. We will move these packages to the new archive site where users can continue to download them.

Note that package managers will no longer be able to download packages for these versions. To help you update existing systems to minimize impact when we stop publishing versions that have reached EoL, please see the list of impacted versions below:

  • Fedora: 29, 30, 31, 32, 33, 34, 35, 36, and 37*, (*Fedora 37 will reach EoL status November 2023)
  • Ubuntu: Eoan, Hirsute, Impish, Groovy, and Kinetic
  • Debian: Jessie and Stretch

»Special case: RHEL

Systems will need to be updated to use the major versions of Red Hat Enterprise Linux (RHEL) (7, 8, and 9) see our Official Packaging Guide for the appropriate hashicorp.repo configuration. While they are not EoL versions, as part of this effort we are also removing the minor version aliases of RHEL, which include:

  • 7Server, 7Workstation, 7.7, 7.8, 7.9, 8.1, 8.2, and 8.3

»Archival site

We have migrated our EoL and RHEL minor distributions to the archive site and users can download the packages from there instead of HashiCorp will no longer be responsible for maintaining the EoL/RHEL minor packages on the archive site. Use these packages at your own risk. We highly recommend users migrate to an OS version that is currently supported by package maintainers.

»Linux OS end-of-life policy

We will remove end-of-life Linux versions/releases from {deb|rpm} on a regular basis. We will follow the EoL cycles of each distribution and we will remove support when the distribution OS/version reaches an EoL status announced by the distribution maintainers of Fedora, Debian, RHEL, and Ubuntu. We strongly encourage our users to routinely upgrade to the most stable OS versions or utilize packages on the archive site for deprecated versions to avoid disruptions.


To make these changes as clear as possible, we have created a short FAQ list below:

Q: What changes must practitioners make to continue using Linux packages from HashiCorp?

A: Anyone using EoL distributions will need to upgrade their OS (and existing systems) to continue having package manager support.

Anyone currently changing their repo configs to reference RHEL minor versions will need to revert to major versions. This applies only to HashiCorp repositories, users can continue targeting minor versions for other repos if that suits them.

If users want to use any EoL or RHEL minor distributions, they will need to pull from the archive site instead of the production sites ([apt|rpm] However, we highly encourage users to migrate and use current versions. HashiCorp will not offer official support or publish any updates to fix issues with EoL packages on the archive site.

Q: If a user is running on supported versions of HashiCorp products but on an EoL OS, what is the workaround?

A: Users can install via .zip instead of Linux packages or download the packages manually from and create their own local repo (users can generate their own metadata, allowing their hosts to then use the local repo via package managers).

Q: Will moving EoL versions to the archive site become a regular thing?

A: Yes. This process will become a regular occurance when a distribution version reaches end-of-life status. We will follow the EoL cycles that distribution maintainers have set up for their distributions.

If you have concerns or questions, please create a post on HashiCorp Discuss.

Sign up for the latest HashiCorp news

By submitting this form, you acknowledge and agree that HashiCorp will process your personal information in accordance with the Privacy Policy.