Running “pip install virtualenv” as part of our build_environments step started throwing and error[1] two days ago, which coincided with a new google/cloud-sdk image release[2]. How do I pin an image version, so I can test it’s an issue with the latest image? Here is the docker setup:
docker:
- image: google/cloud-sdk
auth:
username: <redacted>
password: <redacted>
and here is the build_environment step that’s failing on the first command:
- run:
name: build_environment
command: |
pip install virtualenv
virtualenv Venv
source Venv/bin/activate
pip install -r requirements-dev.txt -r requirements.txt
[1]
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Exited with code exit status 1
[2] hub.docker[.]com/r/google/cloud-sdk/