

Git config -global -add safe.directory /srv/provision/utilities/core

To add an exception for this directory, call: [0m[39m[2m* Updating the "core" utility on the "master" branch.[21m[0mįatal: unsafe repository ('/srv/provision/utilities/core' is owned by someone else) Upon checking the logs, in provisioner-utility-source-core.log I can see the following log: [0 38 5 2m ▷ Running the [0m[1m[0 38 5 5m'utility-source-core'[21m[0 38 5 2m provisioner.[0m[0m[0m VagrantĪssumes that this means the command failed. When running vagrant up or vagrant up -provision, I'm receiving the following error: The SSH command responded with a non-zero exit status. I'm running Vagrant version 2.2.19 with VirtualBox version 6.1 on Mac OS Monterey version 12.3.1.
