How to save 'jf docker scan' table output to a file?

[jghal]

I just want to put the table output in a file

$ jf docker scan alpine:3.15
11:38:58 [🔵Info] Log path: /home/jghal/.jfrog/logs/jfrog-cli.2022-10-06.11-38-58.12203.log
The full scan results are available here: /tmp/jfrog.cli.temp.-1665074350-589997432
Note: no context was provided, so no policy could be determined to scan against.
You can get a list of custom violations by providing one of the command options: --watches, --repo-path or --project.
Read more about configuring Xray policies here: https://www.jfrog.com/confluence/display/JFROG/Creating+Xray+Policies+and+Rules
Below are all vulnerabilities detected.
Vulnerabilities
┌──────────┬───────────────────┬───────────┬────────┬──────────┬───────────┬───────────┬───────────────┐
│ SEVERITY │ IMPACTED          │ IMPACTED  │ TYPE   │ FIXED    │ COMPONENT │ COMPONENT │ CVE           │
│          │ PACKAGE           │ PACKAGE   │        │ VERSIONS │           │ VERSION   │               │
│          │                   │ VERSION   │        │          │           │           │               │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🔥High   │ 3.15:libcrypto1.1 │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2021-4044 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🔥High   │ 3.15:libssl1.1    │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2021-4044 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🔥High   │ 3.15:libcrypto1.1 │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1473 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🔥High   │ 3.15:libssl1.1    │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1473 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🎃Medium │ 3.15:libcrypto1.1 │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1343 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🎃Medium │ 3.15:libssl1.1    │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1343 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🎃Medium │ 3.15:libssl1.1    │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1434 │
├──────────┼───────────────────┼───────────┼────────┼──────────┼───────────┼───────────┼───────────────┤
│ 🎃Medium │ 3.15:libcrypto1.1 │ 1.1.1q-r0 │ Alpine │          │ alpine    │ 3.15      │ CVE-2022-1434 │
└──────────┴───────────────────┴───────────┴────────┴──────────┴───────────┴───────────┴───────────────┘
11:39:10 [🔵Info] Scan completed successfully.

into a text file, but redirecting the output gives me this

$ jf docker scan alpine:3.15 > report.txt
11:39:19 [🔵Info] Log path: /home/jghal/.jfrog/logs/jfrog-cli.2022-10-06.11-39-19.12369.log
11:39:31 [🚨Error] inappropriate ioctl for device
$ cat report.txt 
The full scan results are available here: /tmp/jfrog.cli.temp.-1665074370-4152493838
Note: no context was provided, so no policy could be determined to scan against.
You can get a list of custom violations by providing one of the command options: --watches, --repo-path or --project.
Read more about configuring Xray policies here: https://www.jfrog.com/confluence/display/JFROG/Creating+Xray+Policies+and+Rules
Below are all vulnerabilities detected.

and the "full scan results" file /tmp/jfrog.cli.temp.-1665074370-4152493838 is in JSON instead.

[sverdlov93]

Hi @jghal,
You can use --format="simple-json" to print a JSON with the same structure as the table.

[jghal]

thanks

[sverdlov93]

Hi @jghal ,
Thanks for reporting this issue.
Our apologies for the inconvenience caused by this.
This PR - jfrog/jfrog-cli-core#582 should fix it.
I will update this thread once the next release will be out.

[sverdlov93]

Hi @jghal ,
JFrog CLI 2.28.0 is released and should fix the above issue.
Looking forward to your feedback on it.