HashiCorp has announced the end of life of the HCP Vagrant Registry, the service behind Vagrant Cloud box names such as bento/ubuntu-24.04. The dates are in HashiCorp’s end-of-life notice. Once the registry stops serving boxes, a Vagrantfile that names a Vagrant Cloud box can no longer download it.
Vagrant itself does not need the registry. A box can be served from any web server, as long as there is a metadata file that lists its versions. That is how the CloudSOE repository works.
Step 1: Find the boxes you depend on
grep -rn "vm.box" --include=Vagrantfile .
vagrant box list
Boxes already on your machine keep working. The problem appears on a new laptop, in CI, or after vagrant box remove.
Step 2: Change two lines
Before:
config.vm.box = "bento/ubuntu-24.04"
After:
config.vm.box = "cloudsoe/ubuntu-24.04"
config.vm.box_url = "https://boxes.cloudsoe.com/cloudsoe/ubuntu-24.04.json"
The box list shows what is available, with the exact lines for each box.
Step 3: Recreate the machine
vagrant destroy
vagrant up
What to check after the switch
A base box from a different publisher is close to the old one, but not identical. Check these before you rely on it:
- Provider. CloudSOE boxes exist for libvirt and VirtualBox. There is no VMware, Hyper-V or Parallels box.
- Architecture. amd64 only.
- Disk size. The disk is 40 GB. If a provisioner assumed a different size, adjust it.
- Preinstalled packages. The boxes contain the official cloud image plus what Vagrant needs. If your old box shipped extra tools, install them in a provisioner.
- Default CPU and memory. Set them in the Vagrantfile so they do not depend on the box. See getting started.
Hosting your own boxes
If you publish boxes of your own, the same approach works for you: upload the .box files to any static host, and write one JSON metadata file per box with a versions list, each version holding a providers list with name, url, checksum_type and checksum. Point config.vm.box_url at that file. The CloudSOE metadata is a working example.