SAST: bind source path does not exist: /code

Summary

$ sudo docker run -eCI_PROJECT_DIR=/code  --interactive --tty --rm   --volume "$PWD":/code   --volume /var/run/docker.sock:/var/run/docker.sock   registry.gitlab.com/gitlab-org/security-products/sast:2.7.2

2019/11/20 15:07:12 Mount project directory in containers
2019/11/20 15:07:12 [bandit] Detect project using plugin
2019/11/20 15:07:12 [bandit] Project is compatible
2019/11/20 15:07:12 [bandit] Starting analyzer...
2: Pulling from gitlab-org/security-products/analyzers/bandit
Digest: sha256:8f9c8372aa385e2985ef0d667eaf8ffa9126158eb879f40bd758cd8b89bb1987
Status: Image is up to date for registry.gitlab.com/gitlab-org/security-products/analyzers/bandit:2

2019/11/20 15:07:14 Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /code

Steps to reproduce

(How one can reproduce the issue - this is very important)

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

/label ~bug