Check docker image CVEs in vulnerabilities workflow #1480
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
francbartoli
force-pushed
the
feature/scan-docker-image-cves
branch
2 times, most recently
from
3555938 to
37deb57
Compare
Fix working directory Fix working directory Fix working directory
francbartoli
force-pushed
the
feature/scan-docker-image-cves
branch
from
37deb57 to
4529e4f
Compare
Use trivy action
francbartoli
force-pushed
the
feature/scan-docker-image-cves
branch
from
a0f7073 to
014b28d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Check CVEs in the Docker image via trivy. Limitations:
Related issue / discussion
#1479
Additional information
None
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)