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
Hi there, with the recent release of the actions version 0.0.19 we are seeing our actions failing for scan error: image scan failed: failed analysis: analyze error: failed to analyze layer: sha256:87ceb75dec9b514f26b1b9227e29d4f72790c37a5c1c3281efe349dda702e544 : config scan error: scan terraform error: terraform scan error: stat /github/workspace/evo-hub-infra/main/variables.tf: no such file or directory
This was working correctly before the version bump.
changing the 'uses: aquasecurity/trivy-action@master' back to 'uses: aquasecurity/trivy-action@0.0.18' causes the issue to no longer be present.
Also able to reproduce this locally, where running with trivy version 0.19.1 causes the same error to be logged, 0.19.2 does not cause this issue to occur.
The text was updated successfully, but these errors were encountered:
Hi there, with the recent release of the actions version 0.0.19 we are seeing our actions failing for
scan error: image scan failed: failed analysis: analyze error: failed to analyze layer: sha256:87ceb75dec9b514f26b1b9227e29d4f72790c37a5c1c3281efe349dda702e544 : config scan error: scan terraform error: terraform scan error: stat /github/workspace/evo-hub-infra/main/variables.tf: no such file or directory
This was working correctly before the version bump.
I believe this issue is relates to aquasecurity/trivy#1120 which is fixed in this PR aquasecurity/trivy#1133.
This was fixed in trivy version 0.19.2
According to https://github.com/aquasecurity/trivy-action/blob/master/Dockerfile we are based off of the 0.19.1 version.
Hopefully bumping the base docker image that is being used should cause this error to be fixed.
For reference we trigger the check in our github actions via:
changing the 'uses: aquasecurity/trivy-action@master' back to 'uses: aquasecurity/trivy-action@0.0.18' causes the issue to no longer be present.
Also able to reproduce this locally, where running with trivy version 0.19.1 causes the same error to be logged, 0.19.2 does not cause this issue to occur.
The text was updated successfully, but these errors were encountered: