jf docker scan Fails Consistently on Previously Working Images Since 23/10/25

[yitzhaktal]

Describe the bug

Hi,

On 25/10/21, we ran the following command successfully: jf docker scan ${{ parameters.image }} --licenses --format=simple-json > ${{ parameters.outputFolder }}/${{ parameters.reportFilenamePrefix }}.jfrog.json It worked without any issues, as it normally does.

However, on 23/10/25, we ran the same command with a different image, and it failed. Initially, we thought the problem was with the new image. But when we reran the exact same command as on 21/10/25 with the original image, it failed as well.

We have reproduced this issue locally multiple times, and it now occurs consistently. Please find attached the debug logs from the failing runs for your reference.

Current behavior

➜ athena git:(dev) ✗ JFROG_CLI_LOG_LEVEL=DEBUG jf docker scan lightruncom/webapp:1.70.2-release.8c297ca52b --licenses --format=simple-json 16:50:58 [Debug] JFrog CLI version: 2.81.0 16:50:58 [Debug] OS/Arch: darwin/arm64 16:50:58 [Debug] Trace ID for JFrog Platform logs: 7efe466e22b4fa7b 16:50:58 [Debug] Using server-id configuration 16:50:58 [Debug] Sending HTTP GET request to: https://lightrun2024.jfrog.io/xray/api/v1/system/version 16:50:58 [Debug] Xray version: 3.131.4 16:50:58 [Debug] Sending HTTP GET request to: https://lightrun2024.jfrog.io/xray/api/v1/xsc/system/version 16:50:59 [Debug] XSC version: 3.999.999 16:50:59 [🔵Info] Log path: /Users/amitshkoory/.jfrog/logs/jfrog-cli.2025-10-26.16-50-59.77261.log 16:51:16 [🔵Info] Trace ID for JFrog Platform logs: 7efe466e22b4fa7b 16:51:16 [🚨Error] failed while parsing the response from Xray: violation doesn't have any components

jfrog-cli.2025-10-26.16-50-59.77261.log debug-logs.log

Reproduction steps

latest jfrog cli version + jf docker scan ${{ parameters.image }} --licenses --format=simple-json > ${{ parameters.outputFolder }}/${{ parameters.reportFilenamePrefix }}.jfrog.json

Expected behavior

A log from working ran is attached.

JFrog CLI version

2.81.0

Operating system type and version

Linux

JFrog Artifactory version

SaaS

JFrog Xray version

SaaS

[yitzhaktal]

@yahavi I opened a ticket as requested, as it looks like a bug

[poprygun]

I am experiencing a similar issue upon upgrading to 2.81.0.

Adding "--fail=false" flag did not help.

Below is the stack trace:

2025-10-28T13:47:08.496Z [jfxia] [WARN ] [] [extractor:70              	] [UnnamedContext              	] Error while reading metadata: err:no metadata found for APKINDEX.a7c09383.tar.gz/DESCRIPTION, Name and Version are empty strings
2025-10-28T13:47:08.509Z [jfxia] [WARN ] [] [extractor:70              	] [UnnamedContext              	] Error while reading metadata: err:no metadata found for APKINDEX.b36168cb.tar.gz/DESCRIPTION, Name and Version are empty strings
2025-10-28T13:47:08.683Z [jfxia] [WARN ] [] [golang:74                 	] [UnnamedContext              	] ldflags did not contain valid version information
2025-10-28T13:47:09.209Z [jfxia] [INFO ] [] [docker:108                	] [UnnamedContext              	] Finished indexing layers of docker /tmp/jfrog.cli.temp.-1761659213-3941422362/16772d4b-2855-466a-b4f8-9dd318f07f28/176165922083163046/ (sha256:520ca69e3a680b992d217d250d88118503537010c954dff8d38183504fbbc0bd)
13:47:09 [Info] Waiting for scan to complete on JFrog Xray...
13:47:36 [Info] Trace ID for JFrog Platform logs: 905822ef286914a9
Error: 6 [Error] failed while parsing the response from Xray: violation doesn't have any components
Error: Process completed with exit code 1.