Bug: Vagrant fails at very early stage after updating to 3.13.2

[luuptekman]

Are you using the latest stable or develop branch version of VVV?

Yes (stable)

Is it a new VVV, or an existing VVV that used to work?

Existing, worked but now broken

Did you use a CustomFile?

No (default)

Whats the problem?

I used git pull to update to latest stable version: 3.13.2.

After that I'm unable to start any vagrant commands such as vagrant up, vagrant ssh etc....Execution ends with the following error:

➜  vvv git:(stable) ✗ vagrant ssh
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/myuser/dev/vvv/Vagrantfile
Line number: 45
Message: Errno::ENOENT: No such file or directory - docker

I noticed this change in Vagrantfile: https://github.com/Varying-Vagrant-Vagrants/VVV/commit/e10bc480339fe5ffb3a8893a5c89e3260131853a#

After modifing line 45 back to if system("docker version") vagrant works again.

About my laptop / vagrant:

• Macbook Pro with Apple chip M3
• Vagrant version 2.4.0
• using Parallels

How do we reproduce it?

No response

What is the output of vagrant status

➜  vvv git:(stable) ✗ vagrant status
__ __ __ __
\ V\ V\ V / v3.13.2 Ruby:3.1.4, Path:"/Users/mrluuptek/dev/vvv"
 \_/\_/\_/  git::stable(e0dad5de)

Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/mrluuptek/dev/vvv/Vagrantfile
Line number: 45
Message: Errno::ENOENT: No such file or directory - docker

Which Operating System are you using?

Apple MacOS (Arm64/Apple Silicon)

Which provider are you using?

Parallels (Apple Silicon/Arm)