🧑‍🌾 doc_ros2doc job build regression due to missing --break-system-packages flag

[Crola1702]

Reference build:

• https://build.ros.org/job/doc_ros2doc/1615/console

Caused by: #5007

Log output:

06:49:47 + docker run --rm --net=host --cidfile=/home/jenkins-agent/workspace/doc_ros2doc/docker_ros2_documentation.cid -v /home/jenkins-agent/workspace/doc_ros2doc/repositories/ros2_documentation:/tmp/doc_repository -v /home/jenkins-agent/workspace/doc_ros2doc/upload_repository:/tmp/upload_repository -e REPO=/tmp/doc_repository -e SITE=/tmp/upload_repository ros2_documentation
06:49:47 
06:49:47 Usage:   
06:49:47   pip3 install [options] <requirement specifier> [package-index-options] ...
06:49:47   pip3 install [options] -r <requirements file> [package-index-options] ...
06:49:47   pip3 install [options] [-e] <vcs project url> ...
06:49:47   pip3 install [options] [-e] <local project path> ...
06:49:47   pip3 install [options] <archive url/path> ...
06:49:47 
06:49:47 no such option: --break-system-packages

Last successful build is building the dockerfile from ubuntu:noble, while the failing builds are building it from ubuntu:jammy

Running pip3 --version in both containers

root@9c98ca9736b1:/# pip3 --version # ubuntu:noble
pip 24.0 from /usr/lib/python3/dist-packages/pip (python 3.12)

root@f42310142408:/# pip3 --version # ubuntu:jammy
pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)

jammy pip3 version does not support --break-system-packages flag

[fujitatomoya]

@Crola1702 i will take a look, thanks.

[christophebedard]

You could use the env var (PIP_BREAK_SYSTEM_PACKAGES=1) instead, since it just gets ignored if it's not known. https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-break-system-packages

[fujitatomoya]

@christophebedard thanks! i think i missed changing Dockerfile.

there are a couple of things we can do here.

• address docker build warnings.
• add github/workflow to make sure docker build and docker run completes any error only if Dockerfile is updated. (if we had this, we would have known this issue before merge)