yarnpkg is no longer available in Debian/bookworm, while we already ship
a bundled yarnpkg. So use that bundled yarnpkg binary also within our
Docker related actions. Also see commit bd8a150825
and MT#55813 (and
related to MT#55391).
Use our yarn binary as /tmp/yarn within Docker (to have to maintain it
only at one place). While at it, switch Docker instructions from ADD to
COPY, quoting from
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#add-or-copy ->
Although ADD and COPY are functionally similar, generally speaking, COPY is preferred.
Also, run pip3 install with --break-system-packages, to address new
PEP 668 specific behavior of pip3, as present in Debian/bookworm:
| 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.
Change-Id: I09774d137925891a5f40e5597c40f48594f41d6f
mr12.0
parent
6b6c9faac8
commit
6767abe0fa
Loading…
Reference in new issue