Dependency scanning job fails silently with "exit status 1"

Summary

The dependency scanning job fails in a project containing a valid requirements.txt file (python project), but doesn't produce any useful output as to why the job failed, simply "exit status 1". The git project contains a requirements.txt file within the root directory of the project. Testing the scanner image directly against the code pointing directly to the requirements.txt file also fails.

Steps to reproduce

Create a project with the following requirements.txt file:

cryptography==3.4.7
boto3==1.17.82
pytest==6.2.4
pytest-cov==2.12.0
numpy==1.20.3
pandas==1.2.4
pycryptodomex==3.10.1
smart-open==5.1.0
ujson==4.0.2

Test the dependency scanning container directly or with CI/CD including the provided template.

What is the current bug behavior?

The dependency scanner fails without any useful output, only "exit status 1".

What is the expected correct behavior?

Dependency scanning report is generated and made available in the security dashboard.

Relevant logs and/or screenshots

Output from the job:

Testing the code directly with the docker container, i.e. outside of the CI/CD pipeline environment.

Jonathans-Mac-Mini:eph-python-base jdurbin$ docker run --rm -it -v $(pwd):/code registry.gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python:2 bash
root@796d8514736e:/# cd /code/
root@796d8514736e:/code# /analyzer run --target-dir /code --artifact-dir dist/ --pip-requirements-file requirements.txt
[INFO] [gemnasium-python] [2021-06-03T10:41:50Z] ▶ GitLab gemnasium-python analyzer v2.18.3
exit status 1

Output of checks

exit status 1