Kali Vagrant Rebuild Released – Preconfigured Command-Line VMs

Kali Vagrant Rebuilt, a streamlined toolchain for building and distributing pre-configured virtual machine (VM) images via HashiCorp Vagrant.

By replacing Packer with an in-house DebOS-based solution, the Kali team has unified its VM build infrastructure, reduced external dependencies, and simplified cross-platform image creation.

The new process ensures quick, unattended VM provisioning and delivers consistent “base box” images ready to deploy through Vagrant’s command-line interface.

Historically, Kali used HashiCorp Packer to assemble VM images: configuring unattended OS installations through preseeding, applying post-install scripts, exporting hypervisor-specific images, and compressing them into .box files.

While powerful, Packer required the target hypervisor to be installed locally—making cross-platform builds difficult, such as generating Hyper-V images on Linux hosts.

To address this complexity, the Kali development team turned to DebOS, an automation framework originally adopted for general VM builds.

With DebOS, the entire VM build pipeline now runs natively on Linux hosts, regardless of the target provider.

The new approach applies a common post-install script to every VM: setting a fixed vagrant username, installing the standard Vagrant public SSH keys, and enabling sudo for effortless root-level actions.

Optional enhancements—such as streamlining SSH for air-gapped environments and standardizing the vagrant password—are also implemented in the same step.

Kali Vagrant Rebuild Released

The result is a single, maintainable build script that outputs both stock and Vagrant-ready images from the same infrastructure, eliminating the need for separate Packer builds.

A critical challenge emerged when Windows hosts expected additional Hyper-V export files (*.vmcx, *.vmrs, and .xml) alongside the Vagrant base box.

Since DebOS builds these images outside Hyper-V, the extra binaries were absent, causing older Vagrant versions to fail on Windows.

Instead of including dummy binaries, the Kali team submitted a merge request to the official Vagrant project.

As of Vagrant v2.4.8 (released August 5, 2025), support for Hyper-V-less base boxes is built in.

Simplified Usage and Continued Packer Support

According to Report, Users running Kali 2025.2 or newer on Windows must upgrade to Vagrant v2.4.8 or later; otherwise they can continue using legacy providers.

To reflect the shift away from Packer, the Kali team has renamed its Git repository from kali-vagrant to kali-packer on GitLab.

However, Packer build scripts remain available and have been refreshed one final time for those who prefer or require the older toolchain.

Users can still clone, modify, and run these scripts if they wish to maintain an independent Packer-based workflow.

For those starting fresh with the new DebOS-driven boxes, the workflow is straightforward:

bash# Add the Kali rolling box for VirtualBox
vagrant box add kalilinux/rolling --provider virtualbox --force --clean --box-version 2025.2.1

# Initialize a minimal Vagrant environment
mkdir -p vagrant-demo && cd vagrant-demo
vagrant init --force --minimal kalilinux/rolling

# Launch and provision the VM
vagrant up --provider virtualbox

# Access the VM via SSH
vagrant ssh

This streamlined process underscores Kali’s commitment to reproducible, automated builds and quick VM provisioning.

By consolidating on DebOS and contributing critical compatibility fixes to upstream Vagrant, Kali Vagrant Rebuilt empowers security professionals and content creators with robust, ready-to-use environments—without leaving the command line.

Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.