The CloudSOE repository hosts Debian Vagrant boxes for the libvirt and VirtualBox providers: Debian 12 (bookworm) and Debian 13 (trixie). The boxes are built from the official Debian cloud images, served from boxes.cloudsoe.com, and free to download without an account.

Available Debian boxes

BoxLatest versionReleasedProvidersArchVerifyUse
cloudsoe/debian-12Debian12202611.15.02026-11-15libvirtVirtualBoxamd64SHA-256How to use →
cloudsoe/debian-13Debian13202611.15.02026-11-15libvirtVirtualBoxamd64SHA-256How to use →

The table is generated from the repository catalogue each time this site is built.

Use a Debian box

Debian 13 (trixie):

Vagrant.configure("2") do |config|
  config.vm.box     = "cloudsoe/debian-13"
  config.vm.box_url = "https://boxes.cloudsoe.com/cloudsoe/debian-13.json"
end

Debian 12 (bookworm):

Vagrant.configure("2") do |config|
  config.vm.box     = "cloudsoe/debian-12"
  config.vm.box_url = "https://boxes.cloudsoe.com/cloudsoe/debian-12.json"
end
vagrant up --provider libvirt      # or: --provider virtualbox
vagrant ssh

box_url is required. It points at a metadata file listing every version of the box, so vagrant box outdated and vagrant box update work as they do with Vagrant Cloud. The box name alone does not resolve, because these boxes are not on Vagrant Cloud.

Why another Debian box repository

HashiCorp is retiring the HCP Vagrant Registry, which hosts the Vagrant Cloud boxes most Vagrantfiles point at. Projects that use Debian boxes from it need a new source. This repository is one: plain HTTPS files and a metadata file per box, with no registry service in between.

How the Debian boxes are built

  1. The build downloads Debian’s generic cloud image for the release and checks it against the SHA512SUMS file Debian publishes next to it.
  2. It adds what Vagrant needs: the vagrant user with passwordless sudo and the Vagrant SSH key. The VirtualBox box also gets the VirtualBox Guest Additions.
  3. The disk is set to 40 GB. The root filesystem grows to fill it on first boot, and SSH host keys are generated on first boot.
  4. Each box is started with vagrant up and checked: login, sudo, disk size, host keys and the /vagrant synced folder. A box that fails is not published.
  5. The box is uploaded with a SHA-256 checksum, which Vagrant verifies on download.

No other packages are added and no settings are tuned. You get Debian as the Debian cloud team ships it.

Debian 12 or Debian 13

Debian 12Debian 13
Codenamebookwormtrixie
Boxcloudsoe/debian-12cloudsoe/debian-13
libvirt box sizeabout 425 MBabout 410 MB
VirtualBox box sizeabout 475 MBabout 620 MB

Use the release your servers run. If you have no constraint, Debian 13 is the newer release.

Which provider to choose

libvirtVirtualBox
HostLinux with KVMLinux, Windows, Intel Mac
Plugin neededvagrant-libvirtnone
Synced folderNFS or rsyncVirtualBox shared folder

Both boxes of a release contain the same Debian. On a Linux host that already runs KVM, use libvirt. VirtualBox is the choice on Windows and on Intel Macs.

Debian on KubeVirt and OpenShift Virtualization

The same repository carries Debian images for KubeVirt, as a containerdisk and as a qcow2 for CDI import. See Debian images for KubeVirt.

Common questions

Is there an arm64 Debian box?

Not yet. The boxes are amd64 only, so they do not run on Apple silicon.

Which Debian releases are covered?

Debian 12 and Debian 13. The table above lists what is published, and each box page shows its versions and checksums.

Can I pin a version?

Yes. Set config.vm.box_version. See pin, update and verify boxes.

Are these official Debian boxes?

No. They are built by CloudSOE from the official Debian cloud images. Debian is a registered trademark of Software in the Public Interest, Inc., and CloudSOE is not affiliated with or endorsed by the Debian project.

Next steps