Vagrant Workshop – Overview

Overview

This workshop covers the path from fundamentals to repeatable team labs, provider operations, provisioning, security review and incident response.

The focus is on:

Check the box source in the HCP Vagrant Registry or an internal registry
Version the Vagrantfile and review changes like infrastructure code
Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt
Bind forwarded ports to 127.0.0.1 by default and review public networks separately
Write provisioners idempotently and keep package installation reproducible
Limit synced folders to the minimum required paths and never sync secrets
Roll out box updates through controlled testing instead of implicit team upgrades
Treat plugins as supply-chain components and document their versions
Use snapshots as lab helpers, not as a backup replacement
Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Quickstart

# Workshop content is provided through the Orthevs Academy.
chmod +x scripts/provision_vagrant.sh
./scripts/provision_vagrant.sh --dry-run
./examples/00-lab-skeleton/run.sh

Audience

Developers, DevOps engineers, platform engineers, SREs, administrators, security engineers and tech leads who want to standardize local or team-wide development environments with Vagrant.

Learning Path

Level	Focus	Outcome
Fundamentals	Vagrant CLI, Vagrantfile, Boxen, Single-VM-Workflow und sichere Lab-Bedienung	You can explain, review, validate and operate Vagrant environments safely.
Intermediate	Provider, Netzwerke, synced folders, Provisioner und Multi-Machine-Topologien	You can explain, review, validate and operate Vagrant environments safely.
Professional	Team-Standards, Box-Lifecycle, CI-Validierung, Registry-Nutzung und reproduzierbare Umgebungen	You can explain, review, validate and operate Vagrant environments safely.
Advanced Security	Trust-Modell, Box-Provenienz, SSH, Secrets, Plugins, Netzwerkexposition und Incident Response	You can explain, review, validate and operate Vagrant environments safely.

Official Documentation

Practice Appendix: README competency cards

The following cards are intended for repetition, review and coaching. Each card has a concrete Vagrant angle and can be used as a short exercise, pairing prompt or pull-request comment.

Card 001: Check the box source in the HCP Vagrant Registry or an internal registry

Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant init.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 002: Version the Vagrantfile and review changes like infrastructure code

Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant validate.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 003: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant up.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 004: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant status.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 005: Write provisioners idempotently and keep package installation reproducible

Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh.
Review question: Which provisioners run with root privileges and are they idempotent?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 006: Limit synced folders to the minimum required paths and never sync secrets

Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh-config.
Review question: Which plugins are required and how are they versioned?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 007: Roll out box updates through controlled testing instead of implicit team upgrades

Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant provision.
Review question: Which host resources are consumed during vagrant up?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 008: Treat plugins as supply-chain components and document their versions

Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant reload.
Review question: What is the recovery path for a broken VM, box regression or SSH failure?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 009: Use snapshots as lab helpers, not as a backup replacement

Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant halt.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 010: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant destroy.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 011: Check the box source in the HCP Vagrant Registry or an internal registry

Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box list.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 012: Version the Vagrantfile and review changes like infrastructure code

Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box update.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 013: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant plugin list.
Review question: Which provisioners run with root privileges and are they idempotent?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 014: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant snapshot save.
Review question: Which plugins are required and how are they versioned?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 015: Write provisioners idempotently and keep package installation reproducible

Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant init.
Review question: Which host resources are consumed during vagrant up?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 016: Limit synced folders to the minimum required paths and never sync secrets

Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant validate.
Review question: What is the recovery path for a broken VM, box regression or SSH failure?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 017: Roll out box updates through controlled testing instead of implicit team upgrades

Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant up.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 018: Treat plugins as supply-chain components and document their versions

Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant status.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 019: Use snapshots as lab helpers, not as a backup replacement

Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 020: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh-config.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 021: Check the box source in the HCP Vagrant Registry or an internal registry

Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant provision.
Review question: Which provisioners run with root privileges and are they idempotent?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 022: Version the Vagrantfile and review changes like infrastructure code

Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant reload.
Review question: Which plugins are required and how are they versioned?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 023: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant halt.
Review question: Which host resources are consumed during vagrant up?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 024: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant destroy.
Review question: What is the recovery path for a broken VM, box regression or SSH failure?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 025: Write provisioners idempotently and keep package installation reproducible

Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box list.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 026: Limit synced folders to the minimum required paths and never sync secrets

Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box update.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 027: Roll out box updates through controlled testing instead of implicit team upgrades

Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant plugin list.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 028: Treat plugins as supply-chain components and document their versions

Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant snapshot save.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 029: Use snapshots as lab helpers, not as a backup replacement

Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant init.
Review question: Which provisioners run with root privileges and are they idempotent?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 030: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant validate.
Review question: Which plugins are required and how are they versioned?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 031: Check the box source in the HCP Vagrant Registry or an internal registry

Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant up.
Review question: Which host resources are consumed during vagrant up?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 032: Version the Vagrantfile and review changes like infrastructure code

Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant status.
Review question: What is the recovery path for a broken VM, box regression or SSH failure?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 033: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 034: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant ssh-config.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 035: Write provisioners idempotently and keep package installation reproducible

Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant provision.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 036: Limit synced folders to the minimum required paths and never sync secrets

Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant reload.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 037: Roll out box updates through controlled testing instead of implicit team upgrades

Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant halt.
Review question: Which provisioners run with root privileges and are they idempotent?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 038: Treat plugins as supply-chain components and document their versions

Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant destroy.
Review question: Which plugins are required and how are they versioned?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 039: Use snapshots as lab helpers, not as a backup replacement

Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box list.
Review question: Which host resources are consumed during vagrant up?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 040: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant box update.
Review question: What is the recovery path for a broken VM, box regression or SSH failure?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 041: Check the box source in the HCP Vagrant Registry or an internal registry

Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant plugin list.
Review question: Which box is used, who maintains it and which version is approved?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 042: Version the Vagrantfile and review changes like infrastructure code

Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant snapshot save.
Review question: Which provider is required and which host permissions does it need?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 043: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant init.
Review question: Which forwarded ports, private networks or public networks are opened?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 044: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
Check command: vagrant validate.
Review question: Which files are synced between host and guest?
Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.