==> default: Running provisioner: extension-source-core (shell)...
default: Running: /var/folders/rk/8lyzpk2n3xn53wzm7tgjklrh0000gn/T/vagrant-shell20220413-99457-ymejyk.sh
default: ▷ Running the 'extension-source-core' provisioner...
default: * Updating the "core" extension on the "master" branch...
default: fatal: unsafe repository ('/srv/provision/extensions/core' is owned by someone else)
default: To add an exception for this directory, call:
default:
default: git config --global --add safe.directory /srv/provision/extensions/core
default: ! The 'extension-source-core' provisioner ran into problems, the full log is available at '/var/log/provisioners/2022.04.13_12-01-03/provisioner-extension-source-core.log'. It completed in 0 seconds.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Possible Solution
This looks to be related to: CVE-2022-24765
Searching, there are several other projects with similar issues - e.g. https://github.com/actions/checkout/issues/760
I'm guessing when I provisioned, Git was updated within the VM so it's failed today when I tried provisioning again.
I've tried git config --global --add safe.directory /srv/provision/extensions/core within the VM but it doesn't solve the issue; directory permissions look as I'd expect (all owned by the vagrant user), but I think the provision process runs are root?
Steps to Reproduce (for bugs)
Update git to 2.35.2 or later; try reprovisioning.
Your Environment
I've tried this in both the stable & develop branches of VVV.
Mte90
commented
2 years ago
What was The Command Used To Provision
What Kind of VVV Provision Was This
This was a reprovision of an already working VVV
Logs/What Broke
Possible Solution
This looks to be related to: CVE-2022-24765 Searching, there are several other projects with similar issues - e.g. https://github.com/actions/checkout/issues/760 I'm guessing when I provisioned, Git was updated within the VM so it's failed today when I tried provisioning again.
I've tried
git config --global --add safe.directory /srv/provision/extensions/corewithin the VM but it doesn't solve the issue; directory permissions look as I'd expect (all owned by the vagrant user), but I think the provision process runs are root?Steps to Reproduce (for bugs)
Update git to 2.35.2 or later; try reprovisioning.
Your Environment
I've tried this in both the stable & develop branches of VVV.