Test.dockerfile throwing an error while building.

[Chris Halbert]

Describe the bug
I was trying to run tests locally following the instructions in the CONTRIBUTING.md. The first step of building the docker image fails due to PEP668, but this can be overridden.

To Reproduce
Steps to reproduce the behavior:

1. Clone the repo.
2. In the root of the repo, run docker build -f ${PWD}/test/docker/Test.dockerfile ${PWD}/test/docker/ -t vault-helm-test
3. You will see the output in the Actual Behavior below.

Expected behavior
You should see that the [+] Building 87.2s (13/13) FINISHED or something along those lines after step 2 of reproducing.

Actual Behavior

 > [4/9] RUN pip install yq:
1.437 error: externally-managed-environment
1.437
1.437 × This environment is externally managed
1.437 ╰─>
1.437     The system-wide python installation should be maintained using the system
1.437     package manager (apk) only.
1.437
1.437     If the package in question is not packaged already (and hence installable via
1.437     "apk add py3-somepackage"), please consider installing it inside a virtual
1.437     environment, e.g.:
1.437
1.437     python3 -m venv /path/to/venv
1.437     . /path/to/venv/bin/activate
1.437     pip install mypackage
1.437
1.437     To exit the virtual environment, run:
1.437
1.437     deactivate
1.437
1.437     The virtual environment is not deleted, and can be re-entered by re-sourcing
1.437     the activate file.
1.437
1.437     To automatically manage virtual environments, consider using pipx (from the
1.437     pipx package).
1.437
1.437 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.
1.437 hint: See PEP 668 for the detailed specification.

Environment

• Host: WSL2
• Docker: 24.0.7

[Chris Halbert]

Here's the quick easy fix: #988