All Collections
Running HawkScan
'No default configuration file' error when running the HawkScan CLI
'No default configuration file' error when running the HawkScan CLI

Troubleshooting permissions issues when running HawkScan

Anthony Stinn avatar
Written by Anthony Stinn
Updated over a week ago

Issue

When running the HawkScan CLI via hawk scan, the scan fails immediately with the following error:

General Configuration Error: No default configuration file (stackhawk.yml,stackhawk.yaml) found in [YOUR_CURRENT_WORKING_DIRECTORY]

Cause

stackhawk.yml is not in the current working directory from which hawk scan was run.


Solution

Place stackhawk.yml in the directory from which hawk scan will be run (preferably, the root of the repository for the application in question), and ensure that it has sufficient permissions for the user running hawk.

Also, check the name of the yml file -- if the name is something other than stackhawk.yml or stackhawk.yaml, this is a support configuration but you'll need to specify the file name in the hawk command. For example:

  • hawk scan custom_config.yml


Additional Information

A similar error can occur in Docker-based HawkScan, but which references the /hawk directory -- see 'No default configuration file' error when running Docker-based HawkScan.


Did this answer your question?