Unable to start SITL using Vagrant, sim_vehicle.py: command not found

Hi

I am trying to run ArudCopter SITL in Vagrant by following this tutorial: Setting up SITL using Vagrant — Dev documentation

I am stuck on the step in the instructions where is says to run

vagrant ssh -c "sim_vehicle.py -j 2 -v ArduCopter"

I get

bash: sim_vehicle.py: command not found
Connection to 127.0.0.1 closed.

I have a Git Bash terminal open in /c/Code/Master/ardupilot/Tools/vagrant on my Windows 10 machine.

The previous command

vagrant@ubuntu-bionic:/vagrant$ git submodule update --init --recursive

seemed to run well and I ended by writing “exit” as instructed.

Any tips? I saw that you were active in some related threads @peterbarker so tagging you here

If it is of any use, this is what I get when running “vagrant up” now

toniv@LAPTOP-TU55PHQ7 MINGW64 /c/Code/Master/ardupilot/Tools/vagrant (master)
$ vagrant up
Bringing machine 'bionic64' up with 'virtualbox' provider...
==> bionic64: Checking if box 'ubuntu/bionic64' version '20220424.0.0' is up to date...
==> bionic64: Clearing any previously set forwarded ports...
==> bionic64: Clearing any previously set network interfaces...
==> bionic64: Preparing network interfaces based on configuration...
    bionic64: Adapter 1: nat
==> bionic64: Forwarding ports...
    bionic64: 22 (guest) => 2222 (host) (adapter 1)
==> bionic64: Running 'pre-boot' VM customizations...
==> bionic64: Booting VM...
==> bionic64: Waiting for machine to boot. This may take a few minutes...
    bionic64: SSH address: 127.0.0.1:2222
    bionic64: SSH username: vagrant
    bionic64: SSH auth method: private key
==> bionic64: Machine booted and ready!
==> bionic64: Checking for guest additions in VM...
    bionic64: The guest additions on this VM do not match the installed version of
    bionic64: VirtualBox! In most cases this is fine, but in rare cases it can
    bionic64: prevent things such as shared folders from working properly. If you see
    bionic64: shared folder errors, please make sure the guest additions within the
    bionic64: virtual machine match the version of VirtualBox you have installed on
    bionic64: your host and reload your VM.
    bionic64:
    bionic64: Guest Additions Version: 5.2.42
    bionic64: VirtualBox Version: 6.1
==> bionic64: Mounting shared folders...
    bionic64: /vagrant => C:/Code/Master/ardupilot
==> bionic64: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> bionic64: flag to force provisioning. Provisioners marked to run always will still run.

toniv@LAPTOP-TU55PHQ7 MINGW64 /c/Code/Master/ardupilot/Tools/vagrant (master)

Did you ever solve this issue? Having the same issue on macOS.