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
images/ansible-operator/base.Dockerfile: pin pip3~=21.1
#4877
Conversation
…e split vuln Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com>
/cherry-pick v1.7.x |
@estroz: once the present PR merges, I will cherry-pick it on top of v1.7.x in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick v1.6.x |
@estroz: once the present PR merges, I will cherry-pick it on top of v1.6.x in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @jmrodri |
@@ -0,0 +1,4 @@ | |||
entries: | |||
- description: > | |||
Pinned pip3 to 21.1 in the ansible-operator image to fix https://github.com/pypa/pip/pull/9827 |
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.
This is only kinda user-facing because they may install other python packages using the pre-installed pip3 in their operator's image, i.e. this is only a build vulnerability that most image consumers won't be exposed to.
pip3 must be upgraded because pipenv check
errors otherwise.
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.
/lgtm
@estroz: new pull request created: #4878 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@estroz: new pull request created: #4879 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description of the change:
Motivation for the change: fix unicode split vuln that
pipenv check
complains about/area dependency
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs