You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Unsupported container for the `sysdig-cli-scanner`
2
+
3
+
A few notes:
4
+
* It does a multistep build to get the binary and `chmod`-it from an alpine container, then it uses the debian distroless to save some disk space (the binary itself is 28MB and the image is 31MB)
5
+
* The `sysdig-cli-scanner` version number is used also for the container label
6
+
* The container image itself is scanned by the `sysdig-cli-scanner`!
7
+
8
+
## Run it
9
+
10
+
```
11
+
$ docker run -e SECURE_API_TOKEN="X" ghcr.io/sysdiglabs/sysdig-cli-scanner:1.2.10 --apiurl https://eu1.app.sysdig.com pull://docker.io/sysdiglabs/dummy-vuln-app
12
+
2022-10-28T10:23:05Z Starting analysis with Sysdig scanner version 1.2.10-rc
PACKAGE TYPE VERSION SUGGESTED FIX CRITICAL HIGH MEDIUM LOW NEGLIGIBLE EXPLOIT
38
+
pip python 9.0.1 19.2 0 2 1 0 0 0
39
+
numpy python 1.12.1 1.19.0 0 1 3 0 0 0
40
+
pyxdg python 0.25 0.26 0 1 0 0 0 0
41
+
Jinja2 python 2.11.2 2.11.3 0 0 1 0 0 0
42
+
43
+
POLICIES EVALUATION
44
+
Policy: Sysdig Best Practices FAILED (8 failures)
45
+
46
+
Policies evaluation FAILED at 2022-10-28T10:23:16Z
47
+
Full image results here: https://eu1.app.sysdig.com/secure/#/scanning/assets/results/1722348e04906294017718c0cd082970/overview (id 1722348e04906294017718c0cd082970)
48
+
Execution logs written to: /home/nonroot/scan-logs
49
+
```
50
+
51
+
## Build it
52
+
53
+
The container is built by the [GitHub workflow](../.github/workflows/sysdig-cli-scanner.yaml) but in order to do it manually you can use the [doit.sh](./doit.sh) script. It requires you to be logged in your container image repository (docker login) and modify the REPO variable in the doit.sh script.
0 commit comments