AlmaLinux Moves Its Vagrant Boxes to vagrant.almalinux.org as HashiCorp Retires HCP Vagrant

HashiCorp is retiring the HCP Vagrant registry (formerly Vagrant Cloud), which has hosted the almalinux/* boxes since 2021. To keep them available, AlmaLinux now runs its own catalog at vagrant.almalinux.org, the project announced on November 2. Box names don’t change; Vagrant just needs to be told where to look.

Key dates

• October 1, 2026: HCP stopped accepting new boxes and versions, so AlmaLinux builds since then are only in the new catalog.
• November 2, 2026: HCP Vagrant support ended.
• December 31, 2026: the registry shuts down, and vagrant box add almalinux/9 will fail unless Vagrant points at the AlmaLinux catalog.

How to switch

Set the server URL in your environment:

export VAGRANT_SERVER_URL=https://vagrant.almalinux.org
vagrant init almalinux/10
vagrant up

Or set it in the Vagrantfile, which AlmaLinux recommends for CI jobs that run sudo vagrant up, since sudo drops most environment variables:

Vagrant.configure("2") do |config|
  config.vm.box = "almalinux/10"
  config.vm.box_server_url = "https://vagrant.almalinux.org"
end

If both are set, VAGRANT_SERVER_URL wins.

Boxes you already have

An installed box remembers HCP as its update source, so vagrant box outdated will wrongly say it’s current and will fail once HCP is gone. Re-add it with the catalog set, then prune the old versions:

export VAGRANT_SERVER_URL=https://vagrant.almalinux.org
vagrant box add almalinux/9 --provider libvirt
vagrant box prune --name almalinux/9

Running VMs aren’t affected.

What’s in the catalog

All six boxes are there with full history back to AlmaLinux 8.3 (February 2021): almalinux/10, 10-x86_64_v2, 9, 8, 10-kitten and 10-kitten-x86_64_v2, for libvirt, VirtualBox, VMware, Hyper-V and, on ARM64, Parallels. Releases made after HCP closed, including 9.8, 10.2, the latest Kitten and 8.10 refreshes, plus new VirtualBox boxes for ARM64 hosts such as Apple silicon Macs, are only in the new catalog.

Source: AlmaLinux blog.