The Kali Linux crew has introduced a big enhancement of its Vagrant picture construct course of, streamlining growth and simplifying deployment for customers.
In a transfer to unify its infrastructure, the crew has transitioned from HashiCorp’s Packer to DebOS for producing its pre-configured Vagrant digital machines. The discharge additionally features a helpful cheat sheet to get safety professionals and lovers up and working in minutes.
Vagrant packing containers are pre-packaged VM pictures that permit customers to create, handle, and destroy digital environments totally from the command line, providing a workflow much like containers however for full digital machines. For years, the Kali crew relied on Packer to automate the creation of those pictures.
Whereas efficient, Packer had a notable limitation: it required the host machine to have the goal hypervisor put in, stopping cross-building. As an illustration, constructing a Hyper-V picture was not attainable on a Linux-based construct server.
Recognizing an inefficiency, the event crew determined to consolidate its toolchain. Having already efficiently used DebOS for constructing different Kali VM pictures, they sought to unify the method. “Why do we now have two totally different programs, for a similar goal?” the crew famous of their announcement.
Adapting DebOS for Vagrant builds proved simple. The core necessities for a Vagrant base field are minimal: a set username (vagrant), pre-configured public SSH keys for entry, and sudo privileges.
The Kali crew integrated these requirements, together with really helpful tweaks for person comfort like fastened credentials and SSH optimizations, right into a post-install step inside their current kali-vm construct script. This modification means all Kali VMs, whether or not inventory or Vagrant-specific, at the moment are constructed utilizing the identical automated course of on a centralized Linux infrastructure.
This transition did introduce a problem for Home windows customers working Hyper-V. The brand new DebOS-generated pictures lack sure binary recordsdata (.vmcx/.vmrs) that Packer beforehand included.
Older variations of Vagrant anticipated these recordsdata and would fail upon import. To resolve this, a patch was submitted to the upstream Vagrant mission, which was integrated into a brand new launch.
Consequently, customers wishing to run Kali 2025.2 or newer with Hyper-V should improve their Vagrant set up to model 2.4.8 (launched August 5, 2025) or increased.
To replicate the change, the outdated Packer-based construct scripts have been archived in a renamed Git repository for group members who should want to use them.
To assist customers shortly leverage the brand new pictures, Kali has offered a “cheat-sheet” of instructions. A person can obtain, initialize, and entry a brand new Kali occasion with just some strains of their terminal:
vagrant field add kalilinux/rolling –force –clean –provider virtualbox –box-version 2025.2.1mkdir -pv kali-vagrant/ && cd $_vagrant init kalilinux/rolling –force –minimal –output – –box-version 2025.2.1 | tee Vagrantfilevagrant up –provider virtualboxvagrant ssh
This streamlined launch marks a big inner enchancment for the Kali Linux crew and delivers a extra constant and accessible expertise for its world person base.
Safely detonate suspicious recordsdata to uncover threats, enrich your investigations, and minimize incident response time. Begin with an ANYRUN sandbox trial →
