Testing Ansible with Windows For Windows | Using Molecule, WSL, Vagrant and VirtualBox



Setting up a windows 10 environment to locally test Ansible playbooks written to manage Windows Servers. The focus of this video is more on the setup of the actual environment, rather than testing with molecule which was done in my previous video.

Previous Video: https://youtu.be/xnVr27cgDNI
Github Repo: https://github.com/devopssolver/ansible-molecule-vagrant

Table of Contents:
► 00:12 – The Stack to be Used
► 00:21 – WSL Environment Setup
► 03:04 – Vagrant and Virtual Box setup
► 04:42 – Fix Vagrant version Mismatch
► 05:23 – Running Molecule

Resources:
► jborean93/ansible-windows – https://github.com/jborean93/ansible-windows/blob/master/vagrant/README.md

source

8 thoughts on “Testing Ansible with Windows For Windows | Using Molecule, WSL, Vagrant and VirtualBox”
  1. Thanks for the tutorial. It still needs more steps showing the installation of pip3, pipenv, ansible, and molecule itself.

  2. Hey DevOpsLab, enjoying the video to use Vagrant on WSL2. I am coming across two errors and not sure what to do:
    1.) When I install "sudo vagrant plugin install vagrant-libvirt" I get this error, "ERROR: Failed to build gem native extension."
    2.) From there I saw online the error is probably the version, went through the process you talked on the video at 4:49. I installed the .deb file and dpkg the newest version.It reads like so, "Unpacking vagrant (1:2.2.10) over (1:2.2.10) …
    Setting up vagrant (1:2.2.10) …" However, the version is still showing 2.2.9.

    If you can help me with this I would really appreciate it!

Leave a Reply

Your email address will not be published.

Captcha loading...