Bandit sast timeout without error message
Summary
User run bandit
SAST test and hit time out without much information. Slack discussion: https://gitlab.slack.com/archives/CLA54H7PY/p1587551682183300
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
2020/04/20 19:29:43 [bandit] Starting analyzer...
2020/04/20 19:49:43 Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2020/04/20 19:49:43 Timeout when running the analyzer
When disable dind:
$ /analyzer run
Found project in /builds/group/redacted/project
[main] INFO profile include tests: None
[main] INFO profile exclude tests: None
[main] INFO cli include tests: None
[main] INFO cli exclude tests: None
2008 [0.. 50.. 100.. 150.. 200.. 250.. 300.. 350.. 400.. 450.. 500.. 550..
Running after_script
00:00
WARNING: Failed to inspect build container 4abfe2d5833623459fb1a4454bd2d5d5d54a262e17ae32d0358e1f0ed395fbe5 context deadline exceeded (docker_command.go:77:0s)
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image registry.gitlab.com/gitlab-org/security-products/analyzers/bandit:2 ...
Uploading artifacts for failed job
00:00
Pulling docker image gitlab/gitlab-runner-helper:x86_64-80ffd94f ...
ERROR: Job failed: execution took longer than 1h0m0s seconds
Output of checks
This bug happens on GitLab.com; GitLab Enterprise Edition 13.0.0-pre 075cd4f0
Edited by Cynthia "Arty" Ng