Receiving error while scanning a image

[gopurx]

Tried using both v0 and v0.1 and consistently receiving this error message while running the action.

Scanning for CIS and best practice violations...
Error: Table data must not contain control characters.

Any suggestions on what could be wrong here?

[a-rhote]

We've also been seeing this issue for the past few days. Any pointers on potential trouble shooting ideas, or paths forward would be much appreciated.

[ronanbrowne]

Also seeing this

[ronanbrowne]

After a bit of diffing it seems the issue is this breaking change aquasecurity/trivy#1515

Later versions need to use "trivy image"

e.g. the following works

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock
-v $HOME/Library/Caches:/root/.cache/ aquasec/trivy image python:3.9-slim-buster

[koushdey]

Ronan Browne (@ronanbrowne) We have already migrated the fix. Can you please verify?

[koushdey]

Revanth Gopu (@gopurx) Are you still facing this issue?

[gopurx]

Koushik Dey (@koushdey) Yes, I am experiencing this error. Latest is yesterday. Observation is the image scan outputs when there are CVEs to respond and action error out when there are no CVE to respond.

[gopurx]

Any update on this issue, want to check if I am the only one receiving this error?

[a-rhote]

I'm also still seeing it on my scans.

[koushdey]

Revanth Gopu (@gopurx) Alexis Rhote (@a-rhote) Can you mention the versions you are running? So that I can verify if the fix is present on the version or not. This issue is not reported by many recently.

[a-rhote]

name: Scan image
uses: Azure/container-scan@v0.1
env:
  DOCKER_CONTENT_TRUST: 1
with:
  image-name: <my image>:<tag>
  severity-threshold: HIGH
  run-quality-checks: true

This is what we're using in our ci action definition Koushik Dey (@koushdey)

[gopurx]

Koushik Dey (@koushdey), I tried both v0 and v0.1.

  uses: Azure/container-scan@v0
  with:
      image-name: <my image>:<tag>

[koushdey]

Is it possible to share the image name and tag name used in the action? It's possible that we are getting the issue due to some chars in the input.