AlmaLinux launches independent Vagrant box catalog following HashiCorp registry retirement

AlmaLinux has announced the launch of its own dedicated Vagrant box catalog to replace the service previously provided by HashiCorp's HCP Vagrant registry. This move follows HashiCorp's decision to retire the registry, which has hosted AlmaLinux Vagrant boxes since 2021. The new infrastructure ensures that all historical versions and all future releases remain accessible to developers and system administrators.

Users must update their configurations before the HCP registry shuts down on December 31, 2026, to avoid deployment failures. The migration includes support for multiple architectures, including x86_64 and ARM64, and covers various providers such as libvirt, VirtualBox, and VMware. The new catalog maintains the existing box naming conventions to simplify the transition process.

Migration details and technical implementation

• Configuration Update: Users can redirect Vagrant to the new repository by setting the VAGRANT_SERVER_URL environment variable or by defining config.vm.box_server_url within a Vagrantfile.
• Security and Integrity: The new catalog utilizes the same verification methods as the previous registry, including SHA-256 checksum validation for all downloaded box files.
• Provider and Architecture Support: The catalog hosts six primary box types, including AlmaLinux 8, 9, and 10 (including Kitten), supporting providers like libvirt, VirtualBox, VMware, Hyper-V, and Parallels across x86_64 and ARM64 architectures.
• Legacy Compatibility: Existing local boxes must be manually re-added using the new catalog URL and then pruned to ensure that 'vagrant box update' commands correctly query the AlmaLinux server instead of the defunct HCP registry.

Why it matters

This migration is critical for DevOps engineers and CI/CD pipelines that rely on AlmaLinux images for automated testing and development environments. By hosting their own catalog, AlmaLinux prevents a breaking change in the ecosystem that would have otherwise halted automated provisioning once the HashiCorp registry goes offline.