Closed mindflayer closed 3 years ago
Hi @mindflayer, this action uses trivy
underneath to scan the container images.
The error seems to be coming from trivy
. Can you please enable debug logs to get more details and open an issue on the trivy repo?
It's interesting because it does not happen if I install trivy
locally (I tried to dpkg -i
their deb
file) and docker pull
my image.
With the debug enabled it does not say much more, unfortunately.
I found the problem. We are using docker/build-push-action@v2
for building and pushing our images.
The settings load
needs to be set to true
to allow your action to scan properly.
Also, since at the moment push
and load
cannot be both set to true
due to
buildx call failed with: error: push and load may not be set together at the moment
I had to leave only load
and "manually" push after the scan.
Hi there, after replacing the base image I've started having this problem:
The previous one was
python:3.9-slim
and the current one isubuntu/ubuntu:impish-21.10_edge
.I am testing out a hardened Docker image from Canonical: https://ubuntu.com/security/docker-images I am assuming this is the root cause just because it is the only big thing I changed today.
The image I created works with our test suite, so I assume that is well-formed.