Published On:
November 03, 2026
Published By:

Greg Borbonus

What AlmaLinux's Vagrant Move Means for Your Test Machines

On November 2, 2026, AlmaLinux announced that its ready-made server images for Vagrant now live on a catalog it runs itself, at vagrant.almalinux.org. AlmaLinux says HashiCorp is shutting down the HCP Vagrant registry on December 31, 2026. If your company uses AlmaLinux for test machines, developer laptops, or automated builds, those jobs can stop finding the image they expect once that date passes.

Vagrant is a tool that starts a practice copy of a server from a saved image, called a box. A developer, a hosting vendor, or a build script can be the one who runs it. You notice it when a release depends on that copy. If you want a senior engineer to find those references and switch them before the cutoff, my Able Retainer is $799 a month for eight hours of senior production time, planned with you. Write me at greg@ableadmins.com and we will put it on the calendar.

What changed, in plain terms

AlmaLinux says HashiCorp is retiring the HCP Vagrant registry. That service used to be called Vagrant Cloud. It has hosted the almalinux boxes since 2021. AlmaLinux now serves every version it published before, plus new releases, from its own catalog.

AlmaLinux, citing HashiCorp, lays out three dates. On October 1, 2026, HCP stopped accepting new boxes and new versions. On November 2, 2026, HCP Vagrant support ends. On December 31, 2026, the registry shuts down. After that, a command such as vagrant box add almalinux/9, or a vagrant up that sets config.vm.box to almalinux/9, fails unless Vagrant is pointed at the AlmaLinux catalog.

HashiCorp's notice from September 17, 2026 matches that timeline. New box and registry creation ended on October 1, 2026. Support and maintenance end on November 2, 2026. Remaining Vagrant deployments are decommissioned on December 31, 2026. The Vagrant command-line tool and the GitHub source repository stay available. The registry itself is what shuts down.

The announcement linked under Sources has AlmaLinux's full account of the move. I am summarizing it here so you can see whether your business needs a change. When the answer is yes, use the Able Retainer and we will do the switch with you.

Who should look

Look here when someone on your side keeps a Vagrantfile, a continuous-integration job, or a written guide that names an almalinux box. A Vagrantfile is the small settings file that tells Vagrant which box to start. A continuous-integration job is an automated build that runs when code changes. Either one can keep calling the old registry long after people have forgotten it is there.

AlmaLinux lists six boxes in the new catalog. They are almalinux/10, almalinux/10-x86_64_v2, almalinux/9, almalinux/8, almalinux/10-kitten, and almalinux/10-kitten-x86_64_v2. Images published after HashiCorp stopped taking new versions are already in that catalog. AlmaLinux names AlmaLinux OS 9.8 (9.8.20261005), 10.2 (10.2.20261012), Kitten 10 (10.20261019.0), and 8.10 (8.10.20261026).

Kitten is AlmaLinux's name for a related build line. Remember the word, then move on. When a filename, a ticket, or a script on your side says almalinux and a version, treat it as something to update before the end of December.

Your public site keeps serving people on the server it already uses. This change shows up where a script or a laptop asks the old registry for an AlmaLinux box. Send a short note to your developer or your IT contact. Ask whether any build still pulls an almalinux box, and ask for the file names when the answer is yes. I am happy to read that note with you.

What to hand your developer

AlmaLinux asks anyone who maintains Vagrantfiles, continuous-integration jobs, or documentation that uses almalinux boxes to switch them to the new catalog before December 31, 2026. The switch uses the environment setting VAGRANT_SERVER_URL or the Vagrant setting config.vm.box_server_url. Both should point at https://vagrant.almalinux.org.

Here is a short list you can paste into that note:

  • Search your repositories and shared docs for almalinux/8, almalinux/9, almalinux/10, almalinux/10-x86_64_v2, and the kitten names above.
  • Search build logs for vagrant box add or vagrant up aimed at those names.
  • Mark every place that still expects the old HashiCorp registry to answer.
  • Point each of those places at https://vagrant.almalinux.org with VAGRANT_SERVER_URL or config.vm.box_server_url.
  • Run one normal build after the change and confirm the box still starts.
  • Update the internal doc or runbook so the next person uses the AlmaLinux catalog.

Make the change while the old registry is still answering, so you can compare a working run with the new setting. After December 31, 2026, a missed reference shows up as a failed download, and that week is slower to sort out. I can walk the list with your developer. The Able Retainer is where we book that time.

How Able can help

I do this work with you, on your schedule. Able Retainer is $799 a month and includes eight hours of senior production time. We use those hours to find the Vagrantfiles and build jobs that still name almalinux boxes, point them at vagrant.almalinux.org, and confirm a build still comes up clean.

Those same hours also cover the rest of your Linux and hosting care for the month. We plan them in advance, so the December cutoff sits on a list with the other care your systems need. Email greg@ableadmins.com, or start from the Able Retainer page, and tell me which environments use AlmaLinux. I will reply with a plain plan and a time we can both keep.

Sources

If this catalog move is sitting on your list, I am glad to take it from here. See the Able Retainer, and write me when you are ready.