Open FloRichardAloeCorp opened 5 months ago
@FloRichardAloeCorp can you check which version of the kubescape image is running?
I believe if you use quay.io/kubescape/kubescape-cli:v3.0.15
it should work.
Then I should check if we need to change action.yml
...
@matthyx the current main of the action uses 3.0.5
Would be nice if the action version gets updates more frequently.
@matthyx the current main of the action uses 3.0.5
Would be nice if the action version gets updates more frequently.
do you think we can use dependabot or renovate for that?
yes, pretty sure. Depandabot would create a PR which bumps the baseimage image. Dependabot for Docker
I'm not sure how aligns with your PR-agent though.
Another update on this. I had the same issue with a private gcp container registry.
I got it solved by updating the kubescape-cli version to 3.0.16 and removing the registry://
here:
https://github.com/kubescape/github-action/blob/main/entrypoint.sh#L149
Otherwise, it seems that kubescape is requesting the image from docker.io
what is wrong in this case.
Any update to this issue?
I am facing issue scanning private GHCR images with the same behavior as others.
The last comment, hinting to remove registry://
and upgrading the base docker image fixed my issue. :pray:
But, it would be nice to officially fix this.
Hello, I can't scan a private image that is stored in ghcr.io.
I've verified the credentials.
Here is the pipeline:
The pipeline step
kubescape/github-action@main
outputs the following error:I think that URL of the targeted registry is wrong.