Ansible local-exec provisioning errors on MacOS

[iknowjason]

│ Error: local-exec provisioner error │ │ with module.velocihelk.null_resource.velociraptor-config, │ on ../modules/velocihelk-vm/3-velociraptor-config.tf line 3, in resource "null_resource" "velociraptor-config": │ 3: provisioner "local-exec" { │ │ Error running command '../modules/velocihelk-vm/velociraptor config generate > ../modules/velocihelk-vm/files/config.yaml': exit status 126. Output: /bin/sh: ../modules/velocihelk-vm/velociraptor: cannot │ execute binary file │ ╵ ╷ │ Error: local-exec provisioner error │ │ with module.ws2019.null_resource.provision-sec_tools, │ on ../modules/ws2019-vm/3-ansible_sec_tools.tf line 26, in resource "null_resource" "provision-sec_tools": │ 26: provisioner "local-exec" { │ │ Error running command 'ansible-playbook -i '../modules/ws2019-vm/hosts.cfg' '../modules/ws2019-vm/playbook.yml'': exit status 1. Output: │ PLAY [windows_servers] *** │ │ TASK [endpoint : Copy the ps1 powershell script] * │ objc[21276]: +[NSCFConstantString initialize] may have been in progress in another thread when fork() was called. │ objc[21276]: +[NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a │ breakpoint on objc_initializeAfterForkError to debug. │ ERROR! A worker was found in a dead state