VVV: Bug: Composer provisioner seems to be partially failing
What was The Command Used To Provision
vagrant up
What Kind of VVV Provision Was This
This was a fresh install
Logs/What Broke
Not really sure what to do with this - It has happened twice in a row.
Composer is successfully installed to /home/vagrant and given execute permission.
It seems like the provisioner is failing while trying to change ownership of files in /usr/local/bin. Nothing after this line in the provisioner function is running.
Steps to Reproduce (for bugs)
- New windows machine
- Install virtualbox, vagrant and git
- Open git bash as admin
- Clone vvv, install plugins and run vagrant up
- ???
Provisioning output: https://gist.github.com/ssnepenthe/5efa946668b900ba4808e7cbe98dbf21
Your Environment
Operating System: Windows 11 Vagrant Version: 2.2.19 Virtualbox Version: 6.1.32
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (9 by maintainers)
@ssnepenthe now that it’s been merged are we good to close this? I’ve created #2580 to handle the
npmissue that was surfaced while looking into it as well as #2579 which will let us re-enable parallel hooks