Wednesday, February 14, 2018

ansible vagrant on WSL

Assuming you already have Windows Subsystem for Linux(WSL) running on your host machine.


edition:windows 10 enterprise
version:1709
OS Build:16299.192



sudo apt-get update

sudo apt-get install python-pip git libffi-dev libssl-dev -y

sudo apt-get -f install
sudo apt-get install python-pip git libffi-dev libssl-dev -y

pip install ansible pywinr

Problem:
Collecting pywinr
  Could not find a version that satisfies the requirement pywinr (from versions: )
No matching distribution found for pywinr

cd /mnt/e/PURR/gluster_lab2/

touch test.yml
nano test.yml
ansible-playbook test.yml --connection=local

git clone https://github.com/githubfoam/ansible-vagrant-examples.git
sudo vagrant validate Vagrantfile



$ sudo vagrant up
No usable default provider could be found for your system.

Problem:
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.


http://docs.ansible.com/ansible/latest/intro_windows.html
https://www.jeffgeerling.com/blog/2017/using-ansible-through-windows-10s-subsystem-linux

No comments:

Post a Comment