Update pip install to handle "error: externally-managed-environment" #1320
Conversation
k8s-ci-robot
added
cncf-cla: yes
| echo "$output" | ||
| elif [[ $output == *"error: externally-managed-environment"* ]]; then | ||
| >&2 echo "warning: externally-managed-environment, retrying pip3 install with --break-system-packages" | ||
| pip3 install --disable-pip-version-check --user --break-system-packages "${@}" |
There was a problem hiding this comment.
😆
--break-system-packages
What a great flag name
There was a problem hiding this comment.
Appropriately scary-sounding.
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AverageMarcus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
I don't know for sure. It might just have been a global update to the I did a bit of research on why this is happening and determined it was better just to adapt to it. But I'll go look at #sig-testing and #prow and see if I can find a clue. |
What this PR does / why we need it:
Adds a new
pip3_installbash function that will retry installation if a certain error is raised.Recently the e2e build environment was updated such that PEP 668 became implemented. This means that
pip3 install <package>raises an error telling the user to doapt-get install python-<package>instead. Here is one example of that failure.This makes sense for distro vendors, but image-builder doesn't control the distro and has specific requirements for some tools (Packer, ansible, ansible-lint).
Which issue(s) this PR fixes:
Fixes #
Additional context
I looked at the recommended approach–using a Python virtualenv–but it's not a great fit with our set of scripts and would require more significant refactoring.