Images

A machine names its OS once (vm.os: debian-12). Each target looks that name up in Isoloom's built-in table and uses its own image: a Vagrant box, a Proxmox cloud image, a cloud provider's image. A spec can override the entry for one machine with vm.image.

The built-in table

Vagrant (vagrant target)

Versions are the latest unless pinned (pinned: known to work, or a box rebuilt in place).

Only windows-server-2019 has been booted through Isoloom so far; the other Windows boxes are checked to exist with VirtualBox, VMware and Hyper-V builds.

Proxmox (proxmox target)

Downloaded to the server's image_datastore by Terraform, once per environment.

Isoloom's own steps inside a VM (the no-internet rule, Ansible) install packages with the machine's package manager: apt (Debian, Ubuntu, Kali) or dnf and yum (Rocky, AlmaLinux, CentOS, Fedora).

Docker on one VM (docker-vm, cloud-docker)

The VM only runs Docker, so its image is fixed: the machines' own images come from their docker: part.

Docker (docker target)

No table: each machine's docker: part gives its own image or build.

Overriding one machine

machines:
  dc01:
    vm:
      os: windows-server-2022
      image:
        vagrant: StefanScherer/windows_2022
        vagrant_version: "2021.08.23"

vm.image replaces the built-in entry for that machine on the targets it names; os still decides how Isoloom talks to the machine (SSH or WinRM, sh or PowerShell). Only vagrant and vagrant_version exist today. A target without an entry in vm.image refuses the machine rather than guess.

Next

• vm.image entries for Proxmox and the clouds.
• A user file with your own table (for every spec on your machine), between the built-in table and vm.image.