Prisma Cloud Application Security: How to fix Checkov error - 'Another Thread When Fork() Was Called'

Prisma Cloud Application Security: How to fix Checkov error - 'Another Thread When Fork() Was Called'

3795

Created On 01/08/24 12:18 PM - Last Modified 02/23/24 16:53 PM

Prisma Cloud Compute Twistcli

Public Cloud

Prisma Cloud Compute Edition Self-Hosted

Objective

When executing the Checkov command, users may encounter a error that halts the process:

checkov -d . --external-checks-dir ../../../yaml/s3_versioning/ --download-external-modules true -ca ~/.aws/pge-aws-cert-bundle.pem

Error Overview

objc[69980]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[69980]: +[__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.

Environment

Prisma Cloud
Code Security
Checkov

Procedure

The resolution to this issue is straightforward: simply set the environment variable OBJC_DISABLE_INITIALIZE_FORK_SAFETY to 'YES'.
To do this, execute the following command in your terminal:
```
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
```

Additional Information

View our documentation here on how to add Checkov to Prisma Cloud Application Security.