Vagrant using Trellis on Windows 10 WSL2

trellis
,
20

@cheezman by all means, ask away!

  • Can’t get any sort of provisioning to complete. Neither trellis ssh development, vagrant provision, trellis provision development – and vagrant ssh doesn’t do anything.

trellis ssh development returns:

❯ trellis ssh development
Running command => ssh vagrant@mysite.test
Error running ssh: exit status 255

❯ trellis provision development
Starting galaxy role install process
- composer (1.9.0) is already installed, skipping.
- ntp (2.3.1) is already installed, skipping.
- logrotate (v0.0.5) is already installed, skipping.
- swapfile (v2.0.36) is already installed, skipping.
- mailpit (v1.0.0) is already installed, skipping.

Running command => ansible-playbook dev.yml --inventory-file=.vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory -e env=development

PLAY [WordPress Server: Install LEMP Stack with PHP and MariaDB MySQL] *********

TASK [Gathering Facts] *********************************************************
[WARNING]: Unhandled error in Python interpreter discovery for host default:
Failed to connect to the host via ssh: ssh: connect to host 172.18.208.1 port
2222: Connection timed out
fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Data could not be sent to remote host \"172.18.208.1\". Make sure this host can be reached over ssh: ssh: connect to host 172.18.208.1 port 2222: Connection timed out\r\n", "unreachable": true}

PLAY RECAP *********************************************************************
default                    : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

exit status 4

There appears to be issues with connecting via ssh.

  • vagrant_ip in vagrant.default.yml:
    vagrant_ip: '192.168.56.5'

  • The lines I’ve shared are NOT present in my Windows hosts (C → Windows → System32 → drivers → etc - > hosts)

Upon reading up on this, I found this thread from '22 Trellis hanging on installing dependencies - #23 by dannytaki

I tried what seemed to be the solution:

To try another mount type, create a vagrant.local.yml file and add this:

vagrant_mount_type: virtualbox

It hasn’t really done anything.