-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed various docker vulnerabilities #66
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is merged without the tag changes i think we should have a discussion at the team meeting about manual controll of version updates and the time cost of retaining a high level control.
I'll accept your suggestions, but I think it would be good to still have a verbal chat about this. Perhaps on the next bi-weekly meeting? |
Co-authored-by: Fredrik <fdyrvold@outlook.com>
CHANGELOG.md
file, according to docs:https://iver-wharf.github.io/#/development/changelogs/writing-changelogs
Summary
make
andpython
. They were introduced pre-GitHub with no comment on why they were needed. The docker build succeeds without them, so gone they go.libgcrypt
fromnginx
Docker base image.Motivation
Resolve vulnerability issues reported by
trivy
, which is used to scan in both quay.io and harbor.